Get external service dependencies: which services this one calls (outgoing) and which call it (incoming). Use to understand a single service
AI agents call get_service_deps to retrieve information from Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing dependency graph data to answer questions about service architecture. It has no side effects, does not modify code, execute operations, or delete data. It is a straightforward information-gathering tool similar to 'list' or 'fetch', fitting the Read category with low severity.
From the tool's definition Tool description states 'Get external service dependencies' and 'Use to understand a single service' — purely queries/retrieves dependency information with no modification, creation, or execution of code or services.
Documented attack patterns abuse exactly the kind of access get_service_deps gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for get_service_deps:
{
"version": "1",
"default": "deny",
"tools": {
"get_service_deps": {}
}
}get_service_deps 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 external service dependencies: which services this one calls (outgoing) and which call it (incoming). Use to understand a single service. 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_service_deps: 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_service_deps 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_service_deps 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_service_deps. 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_service_deps 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.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.