AI agents use pathrule_create_workspace 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.
The 'create' prefix indicates a Write operation that generates new data structures. Within the Pathrule server's domain (team memories, rules, skills for AI coding agents), creating a workspace likely instantiates new organizational or configuration entities. This is reversible (can be deleted via sibling tools like pathrule_delete_*), not destructive.
From the tool's definition Tool name 'pathrule_create_workspace' indicates creation of a workspace resource. Description is empty, but the 'create' verb and context of a team memory/rules/skills server suggests reversible creation of new workspace configurations or environments.
Attacks that exploit this kind of access
pathrule_create_workspace. 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_create_workspace: 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_create_workspace 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_create_workspace 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_create_workspace. 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_create_workspace 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 →