disable_trace · MCPEmulate MCP: Risk & Policy

WHAT IT DOES

What disable_trace does on MCPEmulate

AI agents invoke disable_trace to trigger actions in MCPEmulate. 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.

WHY IT NEEDS A POLICY

Why disable_trace needs a policy

This tool modifies the operational state of an emulator session by turning off execution tracing. It is a control/configuration action within an emulation environment (Execute category), as it affects how the emulator runs. The blast radius is low since disabling tracing only affects observability/debugging capability within an isolated emulation session, not data integrity or external systems.

From the tool's definition 'Disable execution tracing' — modifies the state of an active emulation session's tracing feature

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_trace Rate-limited

disable_trace 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": {
    "disable_trace": {
      "limits": [
        {
          "counter": "disable_trace_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCPEmulate, so you can run agents against it safely.

FAQ

Questions about disable_trace

What does the disable_trace tool do? +

Disable execution tracing. It is categorised as a Execute tool in the MCPEmulate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on disable_trace? +

Register the MCPEmulate MCP server in PolicyLayer and add a rule for disable_trace: 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 MCPEmulate. Nothing to install.

What risk level is disable_trace? +

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

Can I rate-limit disable_trace? +

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

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

disable_trace is provided by the MCPEmulate MCP server (labguy94/mcpemulate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.