Get complete information about a specific tool including all details.
AI agents call tool_info to retrieve information from UTCP-MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about registered tools. It does not create, modify, delete, or execute anything; it only fetches and presents information. This is a classic Read category operation.
From the tool's definition Tool description states 'Get complete information about a specific tool including all details' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access tool_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UTCP-MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_info:
{
"version": "1",
"default": "deny",
"tools": {
"tool_info": {}
}
}tool_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get complete information about a specific tool including all details. It is categorised as a Read tool in the UTCP-MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the UTCP-MCP Bridge MCP server in PolicyLayer and add a rule for tool_info: 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 UTCP-MCP Bridge. Nothing to install.
tool_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tool_info 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_info. 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_info is provided by the UTCP-MCP Bridge MCP server (universal-tool-calling-protocol/utcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 UTCP-MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 UTCP-MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.