Execute any tool on any MCP server with proper argument validation
AI agents invoke tool_invoke to trigger actions in 1MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This is a meta-tool that can invoke arbitrary actions on any MCP server in the aggregated pool. Even with "proper argument validation," it enables execution of any operation (Read, Write, Destructive, Financial) depending on what tools exist on connected servers.
From the tool's definition Tool description explicitly states "Execute any tool on any MCP server" — this permits arbitrary execution across all connected MCP servers. The phrase "any tool on any MCP server" indicates unrestricted command execution capabilities.
Documented attack patterns abuse exactly the kind of access tool_invoke gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_invoke:
{
"version": "1",
"default": "deny",
"tools": {
"tool_invoke": {
"limits": [
{
"counter": "tool_invoke_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}tool_invoke stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute any tool on any MCP server with proper argument validation. It is categorised as a Execute tool in the 1MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1MCP Server MCP server in PolicyLayer and add a rule for tool_invoke: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 1MCP Server. Nothing to install.
tool_invoke is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tool_invoke rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for tool_invoke. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
tool_invoke is provided by the 1MCP Server MCP server (1mcp-app/agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 1MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 1MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.