get_contract_versions

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-contract-versions.md

WHAT IT DOES

What get_contract_versions does on Trace

AI agents call get_contract_versions 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.

RISK

Why get_contract_versions is rated Low

This tool retrieves and queries API contract version history with breaking change detection analysis. It performs no writes, deletes, executions, or financial operations. The read-only confirmation in the description and passive comparison operation definitively place this in the Read category with low severity since it only surfaces historical metadata about API contracts.

From the tool's definition Tool name and description clearly indicate 'Read-only' operation that 'Show version history' and 'Compares request/response schemas' to detect changes. Returns historical data in JSON format with no mutation or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_contract_versions 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_versions, this is the rule to start with:

get_contract_versions Allowed

get_contract_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_contract_versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_contract_versions call is checked against it from then on.

FAQ

Questions about get_contract_versions

What does the get_contract_versions tool do? +

Show version history for a service API contract with breaking change detection between versions. Compares request/response schemas across snapshots to flag removed fields, type changes, and renames. Use to review API evolution. For current spec-vs-code drift use get_contract_drift instead. Read-only. Returns JSON: { service, versions: [{ version, date, breakingChanges }] }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_contract_versions? +

Register the Trace MCP server in PolicyLayer and add a rule for get_contract_versions: 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.

What risk level is get_contract_versions? +

get_contract_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_contract_versions? +

Yes. Add a rate_limit block to the get_contract_versions 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.

How do I block get_contract_versions completely? +

Set action: deny in the PolicyLayer policy for get_contract_versions. 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.

What MCP server provides get_contract_versions? +

get_contract_versions 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.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →