set_pull_state · Tangled MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_pull_state does on Tangled MCP Server

AI agents use set_pull_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_pull_state needs a policy

Setting a pull request state (e.g., open, closed, merged, draft) modifies existing data reversibly—pull requests can be reopened or have their state changed again. This is a Write operation rather than Destructive because state changes are not irreversible.

From the tool's definition Tool name 'set_pull_state' indicates modification of pull request state. Context shows this is part of a git collaboration platform with issue and pull request management capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_pull_state Rate-limited

set_pull_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_pull_state": {
      "limits": [
        {
          "counter": "set_pull_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_pull_state

What does the set_pull_state tool do? +

set_pull_state. 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_pull_state? +

Register the Tangled MCP Server MCP server in PolicyLayer and add a rule for set_pull_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_pull_state? +

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

Can I rate-limit set_pull_state? +

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

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

set_pull_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_pull_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 →