set_issue_state · Tangled MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_issue_state does on Tangled MCP Server

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

WHY IT NEEDS A POLICY

Why set_issue_state needs a policy

This tool modifies issue state (closed/open) but does not delete or irreversibly destroy data. The operation is reversible—issues can be toggled between states. This fits the Write category (creates or modifies data reversibly) rather than Destructive.

From the tool's definition Tool description states it can 'close or reopen an issue', which are state-change operations that modify issue metadata. The verb 'set' combined with 'state' indicates a reversible update operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_issue_state Rate-limited

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

FAQ

Questions about set_issue_state

What does the set_issue_state tool do? +

close or reopen an issue. It is categorised as a Write tool in the Tangled 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 set_issue_state? +

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

What risk level is set_issue_state? +

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

Can I rate-limit set_issue_state? +

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

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

set_issue_state is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

set_issue_state is one line of Tangled MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →