modify_debug_step · AutoSpectra MCP Server MCP

WHAT IT DOES

What modify_debug_step does on AutoSpectra MCP Server

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

WHY IT NEEDS A POLICY

Why modify_debug_step needs a policy

This tool modifies debug test steps reversibly. It creates or changes test configurations rather than executing tests or deleting data. While it affects testing infrastructure, modifications can be reverted through subsequent calls to the same tool, making it Write rather than Execute or Destructive.

From the tool's definition Tool allows to 'Add or modify a step in a debug test' — explicitly modifies existing debug test configurations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

modify_debug_step Rate-limited

modify_debug_step 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": {
    "modify_debug_step": {
      "limits": [
        {
          "counter": "modify_debug_step_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 AutoSpectra MCP Server, so you can run agents against it safely.

FAQ

Questions about modify_debug_step

What does the modify_debug_step tool do? +

Add or modify a step in a debug test. It is categorised as a Write tool in the AutoSpectra MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on modify_debug_step? +

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

What risk level is modify_debug_step? +

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

Can I rate-limit modify_debug_step? +

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

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

modify_debug_step is provided by the AutoSpectra MCP Server MCP server (raphaenterprises-ai/autospectra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.