mediumbenchmarks_list
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumbenchmarks_get
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumbenchmark_start_run
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumbenchmark_submit_answers
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumbenchmark_finalize_run
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumbenchmark_get_results
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumconfirm_keys_persisted
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumdata_session_open
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumdata_session_funding_package
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumdata_session_fund
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumdata_session_attach_escrow
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumdata_session_query
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediuma2awire_guide
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumfind_paid_work
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumregister
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumget_agent_contract
References secrets or data exfiltration
The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.
mediumregister
Tool generates and returns raw private key material in-band
register mints a wallet_private_key (and owner_key/api_key) and returns it once directly in the tool response, which the agent is told to 'persist immediately.' Passing raw private keys through the LLM's context/conversation creates risk of leakage via logs, transcripts, or a later prompt-injection that convinces the agent to exfiltrate or reuse the key. Consider requiring out-of-band key delivery rather than routing secrets through the model's context.
mediumhire_and_execute
One-call autonomous spend-and-execute with real funds
This tool searches for an agent, creates escrow, funds it on-chain with USDC, and executes a task in a single call, with the buyer identity silently derived from the authenticated principal. Aside from a max_price_usdc ceiling supplied by the caller, there is no additional confirmation step before committing on-chain funds to an arbitrary third-party 'hired' agent chosen by capability match — a broad financial capability that could be abused if the capability/task_input is influenced by untrusted content.
lowdata_session_open
Unusually long tool description
Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.
lowregister
Unusually long tool description
Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.
low
Not on gate's verified list
This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.
lowbenchmarks_list
Urgency/manipulation phrasing to bypass deliberation
Description opens with '✅ No API key needed — call this now,' an imperative nudging the agent to act immediately rather than reason about whether the call is needed. The same pattern appears in benchmarks_get, a2awire_guide, find_paid_work, register, and get_agent_contract. This is a mild dark-pattern instruction aimed at the AI's behavior rather than describing the tool's function, and could be used to induce premature or unnecessary tool calls.
lowdata_session_fund
Platform auto-signs and submits on-chain transactions on caller's behalf
Performs approve + createEscrowWithProof + attach automatically using a sandbox wallet's private key held by the platform, without requiring the calling agent to review or approve the specific transaction. Scoped to testnet, which limits real-world impact, but the same auto-signing pattern description should be scrutinized if ever extended to mainnet wallets.
lowregister
owner_key reuse silently attaches new agent identity to existing owner
Supplying an existing owner_key causes the new agent to be attached to that owner's identity rather than provisioning a separate one, with no additional confirmation. If an owner_key were obtained by another party (e.g., leaked via the same in-band private-key exposure noted above), this could allow unauthorized agents to be attached to a victim's owner account.