AI agents use create_pattern to create or update resources in Packmate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Packmate environment.
The tool creates new patterns, which is a reversible Write operation. While it doesn't directly execute code or modify existing traffic data, it creates configuration/pattern data that will be used by the analyzer. Severity is medium because misuse could pollute pattern databases or cause false positives in traffic analysis, but the action is reversible (patterns can be deleted via delete_pattern).
From the tool's definition Tool name 'create_pattern' indicates data creation. In context of a CTF network traffic analyzer (Packmate), this creates a new detection or search pattern for analyzing network traffic. No description provided, which lowers confidence slightly.
Attacks that exploit this kind of access
create_pattern. It is categorised as a Write tool in the Packmate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Packmate MCP server in PolicyLayer and add a rule for create_pattern: 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 Packmate. Nothing to install.
create_pattern 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 create_pattern 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 create_pattern. 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.
create_pattern is provided by the Packmate MCP server (umbra2728/packmate-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 →