policy_rule_upsert
Create or update a versioned agentic policy rule. Use when defining explicit allow, deny, or human-approval requirements; existing installations remain unchanged until rules and enforcement mode are configured.
This record as markdown: /tools/io-github-ruvnet-claude-flow/policy-rule-upsert.md
What policy_rule_upsert does on Claude Flow
AI agents use policy_rule_upsert to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why policy_rule_upsert is rated Medium
This is a Write operation: it creates new policy rules or modifies existing ones in a reversible manner. The severity is high because policy rules directly control agent permissions and behavior across an enterprise orchestration platform ('hive-mind swarms, neural networks').
From the tool's definition Tool name 'upsert' combined with description 'Create or update a versioned agentic policy rule' indicates reversible create/modify operations.
Attacks that exploit this kind of access
The rule that runs policy_rule_upsert safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For policy_rule_upsert, this is the rule to start with:
policy_rule_upsert 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every policy_rule_upsert call is checked against it from then on.
Questions about policy_rule_upsert
Create or update a versioned agentic policy rule. Use when defining explicit allow, deny, or human-approval requirements; existing installations remain unchanged until rules and enforcement mode are configured. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for policy_rule_upsert: 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 Claude Flow. Nothing to install.
policy_rule_upsert 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 policy_rule_upsert 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 policy_rule_upsert. 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.
policy_rule_upsert is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue