Fetch the full definition for a schema available in the current MCP session
AI agents call get_schema to retrieve information from Echo MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema metadata from the server without modifying, executing, or deleting any data. It is a simple lookup/query operation that allows inspection of available schemas. The blast radius of misuse is minimal—an agent could only learn what schemas exist, not modify system state or cause harm.
From the tool's definition Tool name 'get_schema' and description 'Fetch the full definition for a schema' indicate data retrieval only. The verb 'Fetch' and action of retrieving schema definitions are read-only operations with no side effects.
Documented attack patterns abuse exactly the kind of access get_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Echo MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_schema:
{
"version": "1",
"default": "deny",
"tools": {
"get_schema": {}
}
}get_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.
Fetch the full definition for a schema available in the current MCP session. It is categorised as a Read tool in the Echo MCP MCP Server, which means it retrieves data without modifying state.
Register the Echo MCP server in PolicyLayer and add a rule for get_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 Echo MCP. Nothing to install.
get_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_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_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_schema is provided by the Echo MCP server (zenlixai/echo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Echo MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Echo MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.