AI agents use pathrule_setup 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.
Given the lack of a description, classification relies on the tool name 'setup' in context of a system that manages team memories, rules, and skills. Setup typically involves creating or modifying configuration state. However, without explicit description details, confidence is moderate. The sibling tools show this server handles both read (get_*), write (create_workspace), and destructive (delete_*) operations.
From the tool's definition Tool name is 'pathrule_setup' and the server manages 'memories, rules and skills' with sibling tools including create, delete, get, and goto operations. The 'setup' action implies initial configuration or creation of workspace state.
Attacks that exploit this kind of access
pathrule_setup. 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.
Register the Pathrule MCP server in PolicyLayer and add a rule for pathrule_setup: 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.
pathrule_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pathrule_setup 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.
Set action: deny in the PolicyLayer policy for pathrule_setup. 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.
pathrule_setup 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →