get_contract_drift
Detect mismatches between API spec and implementation: endpoints in spec but not in code, or in code but not in spec. Use to verify API contract accuracy. For reading the contract itself use get_api_contract instead. Read-only. Returns JSON: { service, missingInCode, missingInSpec, total }.
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-contract-drift.md
What get_contract_drift does on Trace
AI agents call get_contract_drift to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_contract_drift is rated Low
This tool retrieves and analyzes contract drift information from existing API specifications and implementations. It is a diagnostic/query operation that detects discrepancies but does not create, modify, or delete any data. The explicit 'Read-only' designation confirms no write or destructive operations occur. Low severity because misuse would at worst generate incorrect analysis output without affecting systems.
From the tool's definition Tool description explicitly states 'Read-only' and performs detection/verification of API specification mismatches. Returns JSON data without modifying anything: { service, missingInCode, missingInSpec, total }. No side effects on code or configuration.
Attacks that exploit this kind of access
The rule that runs get_contract_drift safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_contract_drift, this is the rule to start with:
get_contract_drift is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_contract_drift call is checked against it from then on.
Questions about get_contract_drift
Detect mismatches between API spec and implementation: endpoints in spec but not in code, or in code but not in spec. Use to verify API contract accuracy. For reading the contract itself use get_api_contract instead. Read-only. Returns JSON: { service, missingInCode, missingInSpec, total }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for get_contract_drift: 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 Trace. Nothing to install.
get_contract_drift 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_contract_drift 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_contract_drift. 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_contract_drift is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue