Get the full schema for a specific tool including input validation rules
AI agents call tool_schema to retrieve information from 1MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns metadata about tool schemas. It is a read-only query operation with no side effects, no code execution, no data modification, and no destructive operations. The blast radius of misuse is minimal—an agent could only learn about available tools' input structures, which is informational only. This clearly falls under the Read category.
From the tool's definition Tool name 'tool_schema' and description 'Get the full schema for a specific tool' indicates a retrieval operation that queries schema information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access tool_schema 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_schema:
{
"version": "1",
"default": "deny",
"tools": {
"tool_schema": {}
}
}tool_schema 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 the full schema for a specific tool including input validation rules. It is categorised as a Read tool in the 1MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 1MCP Server MCP server in PolicyLayer and add a rule for 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 1MCP Server. Nothing to install.
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 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 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.
tool_schema 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.