resolve_bug · Mnehmos Synch MCP: Risk & Policy

WHAT IT DOES

What resolve_bug does on Mnehmos Synch

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

WHY IT NEEDS A POLICY

Why resolve_bug needs a policy

This tool creates or modifies bug tracking records by changing a bug's status to 'resolved' and recording a resolution description. This is a reversible write operation—the bug state can potentially be changed again later. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial).

From the tool's definition Tool name 'resolve_bug' and description 'Mark a bug as resolved' indicate modification of bug tracking data. The phrase 'mark as resolved' is a state change operation that updates existing data (reversible via reopening or modification).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_bug Rate-limited

resolve_bug 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": {
    "resolve_bug": {
      "limits": [
        {
          "counter": "resolve_bug_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 Mnehmos Synch, so you can run agents against it safely.

FAQ

Questions about resolve_bug

What does the resolve_bug tool do? +

Mark a bug as resolved with a resolution description. It is categorised as a Write tool in the Mnehmos Synch MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_bug? +

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

What risk level is resolve_bug? +

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

Can I rate-limit resolve_bug? +

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

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

resolve_bug is provided by the Mnehmos Synch MCP server (mnehmos/mnehmos.synch.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.