Get the schema definition for a data type. Use only when you need schema information (field names, types, constraints, valid enum values) to build queries, filters, or add/update records. Do not call for routine data retrieval - read_parquet returns all necessary field information.
AI agents call get_schema to retrieve information from Parquet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_schema is a metadata inspection tool that retrieves structural information about data types without querying actual data or causing any side effects. It reads schema definitions to enable query construction, fitting the Read category. Severity is low because exposure of schema metadata carries minimal risk compared to actual data access, and there are no destructive, financial, or execution-based consequences.
From the tool's definition Tool description states it 'Get[s] the schema definition for a data type' with purpose to retrieve 'field names, types, constraints, valid enum values' for building queries.
Attacks that exploit this kind of access
Get the schema definition for a data type. Use only when you need schema information (field names, types, constraints, valid enum values) to build queries, filters, or add/update records. Do not call for routine data retrieval - read_parquet returns all necessary field information. It is categorised as a Read tool in the Parquet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Parquet MCP Server 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 Parquet MCP Server. 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 Parquet MCP Server MCP server (markmhendrickson/mcp-server-parquet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →