Get complete schema for a specific tool from a specific server, including inputSchema. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName
AI agents call get-tool to retrieve information from MCP Hub MCP Server 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 schema information about other tools in the MCP hub. It performs a read-only lookup operation that returns descriptive data without modifying, executing, or deleting anything. The severity is low because the information returned is already available through discovery mechanisms (find-tools) and poses no risk of unintended side effects.
From the tool's definition Tool description states it 'Get[s] complete schema for a specific tool' — a retrieval operation with no side effects. The description explicitly indicates it fetches and returns tool metadata and inputSchema.
Documented attack patterns abuse exactly the kind of access get-tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Hub MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-tool:
{
"version": "1",
"default": "deny",
"tools": {
"get-tool": {}
}
}get-tool 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 schema for a specific tool from a specific server, including inputSchema. TIP: Use find-tools first to discover the tool and get the correct serverName and toolName. It is categorised as a Read tool in the MCP Hub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Hub MCP Server MCP server in PolicyLayer and add a rule for get-tool: 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 MCP Hub MCP Server. Nothing to install.
get-tool 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 get-tool 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 get-tool. 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.
get-tool is provided by the MCP Hub MCP Server MCP server (warpdev/mcp-hub-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 MCP Hub MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 MCP Hub MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.