disable_coverage · MCPEmulate MCP: Risk & Policy

WHAT IT DOES

What disable_coverage does on MCPEmulate

AI agents use disable_coverage to create or update resources in MCPEmulate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPEmulate environment.

WHY IT NEEDS A POLICY

Why disable_coverage needs a policy

This tool modifies the state of an emulation session by turning off coverage tracking. It is a reversible configuration change (coverage can presumably be re-enabled), so it falls under Write. The blast radius is low since it only affects instrumentation/monitoring within an isolated emulator session, not external systems or data.

From the tool's definition Disable code coverage tracking

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_coverage Rate-limited

disable_coverage stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_coverage": {
      "limits": [
        {
          "counter": "disable_coverage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_coverage

What does the disable_coverage tool do? +

Disable code coverage tracking. It is categorised as a Write tool in the MCPEmulate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on disable_coverage? +

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

disable_coverage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit disable_coverage? +

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

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

disable_coverage 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.