pathrule_write_skill · Pathrule MCP: Risk & Policy

WHAT IT DOES

What pathrule_write_skill does on Pathrule

AI agents use pathrule_write_skill 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_write_skill needs a policy

The name 'write_skill' strongly suggests creating or modifying skill definitions for AI coding agents. This is reversible (skills can be updated or deleted separately), making it a Write operation rather than Destructive or Execute. However, since skills directly affect AI agent behavior, misuse could cause agents to perform unintended actions, warranting high severity.

From the tool's definition Tool name 'pathrule_write_skill' indicates creation or modification of skills. Related sibling tools include 'pathrule_create_workspace', 'pathrule_delete_skill', and 'pathrule_delete_memory', establishing a pattern where 'write_*' tools create/modify data…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pathrule_write_skill Rate-limited

pathrule_write_skill 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_write_skill": {
      "limits": [
        {
          "counter": "pathrule_write_skill_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_write_skill

What does the pathrule_write_skill tool do? +

pathrule_write_skill. 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_write_skill? +

Register the Pathrule MCP server in PolicyLayer and add a rule for pathrule_write_skill: 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_write_skill? +

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

Can I rate-limit pathrule_write_skill? +

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

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

pathrule_write_skill 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.