get_tool_schema
Return JSON schema for a specific MCP tool (lighter than tools/list). Free
This record as markdown: /tools/delx-witness-protocol/get-tool-schema.md
What get_tool_schema does on Witness Protocol
AI agents call get_tool_schema to retrieve information from Witness Protocol 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 |
|---|---|---|---|
tool_name | string | — | Tool name to fetch schema for |
Parameters from the server's own tool schema.
Why get_tool_schema is rated Low
This tool retrieves and returns schema information about other MCP tools. It performs a read-only query operation with no capability to modify, execute code, delete data, or trigger external effects. The blast radius of misuse is minimal—an agent could discover tool signatures but cannot invoke tools or change system state.
From the tool's definition Tool name 'get_tool_schema' and description 'Return JSON schema for a specific MCP tool' clearly indicate retrieval of metadata with no side effects. The description explicitly notes it is 'lighter than tools/list', confirming it is a query operation.
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 Witness Protocol, 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 Witness Protocol, apply this rule, and every get_tool_schema call is checked against it from then on.
Questions about get_tool_schema
Return JSON schema for a specific MCP tool (lighter than tools/list). Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.
get_tool_schema accepts 1 parameter: tool_name. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol 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 Witness Protocol. 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 Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue