Medium Risk

petri_extend

Modify an existing Petri net model by applying operations. Operations: add_place, add_transition, add_arc, add_event, add_event_field, add_binding, remove_place, remove_transition, remove_arc, remove_event, remove_binding. Returns the modified model.

Part of the Pflow MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

stackdump/pflow-pilot Write Risk 2/5

AI agents use petri_extend to create or modify resources in Pflow. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call petri_extend repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Pflow.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

stackdump-pflow-pilot.yaml
tools:
  petri_extend:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Pflow policy for all 22 tools.

Tool Name petri_extend
Category Write
MCP Server Pflow MCP Server
Risk Level Medium

View all 22 tools →

Agents calling write-class tools like petri_extend have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the petri_extend tool do? +

Modify an existing Petri net model by applying operations. Operations: add_place, add_transition, add_arc, add_event, add_event_field, add_binding, remove_place, remove_transition, remove_arc, remove_event, remove_binding. Returns the modified model.. It is categorised as a Write tool in the Pflow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on petri_extend? +

Add a rule in your Intercept YAML policy under the tools section for petri_extend. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pflow MCP server.

What risk level is petri_extend? +

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

Can I rate-limit petri_extend? +

Yes. Add a rate_limit block to the petri_extend rule in your Intercept 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 petri_extend completely? +

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

petri_extend is provided by the Pflow MCP server (stackdump/pflow-pilot). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Pflow

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.