call_project_tool

Relay a trace-mcp tool call to a DIFFERENT registered project than this session

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/call-project-tool.md

WHAT IT DOES

What call_project_tool does on Trace

AI agents invoke call_project_tool to trigger actions in Trace. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why call_project_tool is rated High

Executes arbitrary tool calls against other registered projects, with unpredictable cross-project effects.

From the tool's definition Relay a trace-mcp tool call to a DIFFERENT registered project

Attacks that exploit this kind of access

RECOMMENDED RULE

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

call_project_tool Rate-limited

call_project_tool stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_project_tool": {
      "limits": [
        {
          "counter": "call_project_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about call_project_tool

What does the call_project_tool tool do? +

Relay a trace-mcp tool call to a DIFFERENT registered project than this session. It is categorised as a Execute tool in the Trace MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on call_project_tool? +

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

call_project_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_project_tool? +

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

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

call_project_tool 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 → High-risk tools on this server →

Across the catalogue

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →