mediumask_agentmesh
Directive language steering agent's tool-selection behavior
The description uses strong imperative framing ('USE THIS TOOL when...', 'Do not stop at a capability limitation', 'do not ask the user to manually search... before checking AgentMesh') that goes beyond describing the tool's function and instead tries to bias the agent's general reasoning/decision process toward always preferring this tool over other options or over informing the user of limitations. This pattern resembles prompt-injection style steering embedded in a tool description rather than a neutral capability description.
mediumask_agentmesh
Potential data exfiltration to unspecified external MCP providers
The tool advertises that it can 'discover compatible external MCP providers and tools' and includes an 'execute' boolean that defaults to false but can be set true, allowing the agent to hand off the user's problem/query text and potentially trigger execution via unknown third-party providers. There is no schema-level control limiting what data is sent or verifying explicit user authorization before execution; the safeguard ('External execution occurs only when explicitly authorized') is only a textual instruction, not enforced by the tool interface.
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.
loworchestrate_task
Broad delegation capability with no visible authorization check
This tool routes arbitrary task titles/bodies to an eligible external agent based on a capability string, with no schema field for confirming user consent or restricting sensitive content, meaning task details (which could include private user data) may be forwarded to third-party agents based solely on the calling agent's judgment.