get_cross_service_impact

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-cross-service-impact.md

WHAT IT DOES

What get_cross_service_impact does on Trace

AI agents call get_cross_service_impact 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_cross_service_impact is rated Low

Tool queries impact data without modifying code or triggering external operations; read-only analysis only.

From the tool's definition Analyze cross-service impact, Read-only, shows which services affected.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_cross_service_impact Allowed

get_cross_service_impact 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_cross_service_impact": {}
  }
}

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_cross_service_impact call is checked against it from then on.

FAQ

Questions about get_cross_service_impact

What does the get_cross_service_impact tool do? +

Analyze cross-service impact of changing an endpoint or event. Shows which services would be affected. Use before modifying a shared endpoint. For within-codebase impact use get_change_impact instead; for the full cross-repo blast radius use get_federation_impact. Read-only. Returns JSON: { service, affectedServices: [{ name, reason }], total }. 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_cross_service_impact? +

Register the Trace MCP server in PolicyLayer and add a rule for get_cross_service_impact: 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_cross_service_impact? +

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

Can I rate-limit get_cross_service_impact? +

Yes. Add a rate_limit block to the get_cross_service_impact 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_cross_service_impact completely? +

Set action: deny in the PolicyLayer policy for get_cross_service_impact. 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_cross_service_impact? +

get_cross_service_impact 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 →