pathrule_update_rule · Pathrule MCP: Risk & Policy

WHAT IT DOES

What pathrule_update_rule does on Pathrule

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

WHY IT NEEDS A POLICY

Why pathrule_update_rule needs a policy

The tool updates rules within a path-scoped team memory system for AI coding agents. Updates are reversible (Write category), not irreversible deletions (Destructive). However, modifying rules could affect agent behavior broadly, justifying medium severity. Confidence is moderate due to empty description; higher confidence would require explicit confirmation of its reversibility and scope of impact.

From the tool's definition Tool name 'pathrule_update_rule' indicates modification of rules. Related sibling tools include 'pathrule_create_rule' (inferred Write), 'pathrule_delete_rule' (Destructive), and 'pathrule_get_rule' (Read), positioning this as a Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pathrule_update_rule Rate-limited

pathrule_update_rule 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": {
    "pathrule_update_rule": {
      "limits": [
        {
          "counter": "pathrule_update_rule_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 Pathrule, so you can run agents against it safely.

FAQ

Questions about pathrule_update_rule

What does the pathrule_update_rule tool do? +

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

How do I enforce a policy on pathrule_update_rule? +

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

What risk level is pathrule_update_rule? +

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

Can I rate-limit pathrule_update_rule? +

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

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

pathrule_update_rule is provided by the Pathrule MCP server (pathrule/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.