Show which workspaces are affected by changes in a given workspace. Lists all cross-workspace edges, affected symbols, and the public API surface consumed by other workspaces. Use before modifying shared code in a monorepo. Read-only. Returns JSON: { workspace, public_api, consumed_by, depends_on...
AI agents call get_cross_workspace_impact 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 queries and retrieves cross-workspace dependency information from a pre-built dependency graph. It performs analysis and returns JSON data with no side effects. The 'read-only' designation confirms it has no capability to modify, delete, or execute operations. It is clearly a Read category tool with minimal risk.
From the tool's definition Tool description explicitly states 'Read-only' and 'Lists all cross-workspace edges, affected symbols, and the public API surface' — retrieves dependency information without modifying or executing code.
Documented attack patterns abuse exactly the kind of access get_cross_workspace_impact 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_cross_workspace_impact:
{
"version": "1",
"default": "deny",
"tools": {
"get_cross_workspace_impact": {}
}
}get_cross_workspace_impact 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.
Show which workspaces are affected by changes in a given workspace. Lists all cross-workspace edges, affected symbols, and the public API surface consumed by other workspaces. Use before modifying shared code in a monorepo. Read-only. Returns JSON: { workspace, public_api, consumed_by, depends_on, cross_workspace_edges }. 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_cross_workspace_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.
get_cross_workspace_impact 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_cross_workspace_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.
Set action: deny in the PolicyLayer policy for get_cross_workspace_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.
get_cross_workspace_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.
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.