Get schema and structure information for span recordings on Tusk Drift. Use this tool to: - Understand what fields are available for a specific instrumentation type - See example payloads for HTTP requests, database queries, etc. - Learn what to filter on before querying spans Common package name...
AI agents call get_schema to retrieve information from Tusk Drift MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs only data retrieval operations: fetching schema metadata and example structures from the Tusk Drift system. It has no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—at worst, an agent could retrieve schema information about the system, which is non-sensitive metadata discovery without operational impact.
From the tool's definition Tool retrieves schema and structure information for span recordings, including available fields and example payloads.
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 Tusk Drift 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.
Get schema and structure information for span recordings on Tusk Drift. Use this tool to: - Understand what fields are available for a specific instrumentation type - See example payloads for HTTP requests, database queries, etc. - Learn what to filter on before querying spans Common package names: - http: Incoming HTTP requests (has statusCode, method, url, headers) - fetch: Outgoing HTTP calls - pg: PostgreSQL queries (has db.statement, db.name) - grpc: gRPC calls - express: Express.js middleware spans. It is categorised as a Read tool in the Tusk Drift MCP MCP Server, which means it retrieves data without modifying state.
Register the Tusk Drift 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 Tusk Drift 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 Tusk Drift MCP server (use-tusk/drift-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tusk Drift 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.
6 Tusk Drift MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.