Get the schema of a single data file from the given file location
AI agents call get_schema to retrieve information from MCP Analyst without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's purpose is to inspect and return metadata about a data file's structure. There are no side effects, no code execution, no data modification, and no destructive actions. This is purely informational retrieval, fitting the Read category with low severity since schema inspection poses minimal risk even if misused by an agent.
From the tool's definition Tool retrieves schema information from a data file ('Get the schema of a single data file') without modifying, executing, or deleting anything. This is a read-only query operation.
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 MCP Analyst, 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.
Get the schema of a single data file from the given file location. It is categorised as a Read tool in the MCP Analyst MCP Server, which means it retrieves data without modifying state.
Register the MCP Analyst 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 MCP Analyst. 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 MCP Analyst MCP server (unravel-team/mcp-analyst). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Analyst, 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 MCP Analyst tools catalogued and risk-classified — across an index of 43,000+ MCP servers.