get_tool_schema
Return the ONE full MCP descriptor (name, description, inputSchema) for a tool you found via discover_tools. Then run it with tools/call.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/get-tool-schema.md
What get_tool_schema does on Gateway
AI agents call get_tool_schema to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | exact tool name |
Parameters from the server's own tool schema.
Why get_tool_schema is rated Low
get_tool_schema queries and retrieves structural information about tools. It has no side effects—no code execution, no data modification, no irreversible actions. The action of running the retrieved tool is separate from this schema-retrieval function.
From the tool's definition The tool returns schema metadata: 'Return the ONE full MCP descriptor (name, description, inputSchema) for a tool'. This is a pure read operation that retrieves and exposes tool definitions without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_tool_schema safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tool_schema, this is the rule to start with:
get_tool_schema is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every get_tool_schema call is checked against it from then on.
Questions about get_tool_schema
Return the ONE full MCP descriptor (name, description, inputSchema) for a tool you found via discover_tools. Then run it with tools/call. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
get_tool_schema accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for get_tool_schema: 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 Gateway. Nothing to install.
get_tool_schema 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_schema 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_schema. 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_schema is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue