Create multiple new coding patterns in the database
AI agents use create_patterns to create or update resources in MCPatterns — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPatterns environment.
This tool creates and persists new records in a database. It is a Write operation because it modifies data reversibly—patterns can be updated or deleted later (as evidenced by sibling tools 'delete_patterns' and 'delete_code_examples').
From the tool's definition Tool name 'create_patterns' with description 'Create multiple new coding patterns in the database' indicates data creation and storage operations.
Attacks that exploit this kind of access
Create multiple new coding patterns in the database. It is categorised as a Write tool in the MCPatterns MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPatterns MCP server in PolicyLayer and add a rule for create_patterns: 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 MCPatterns. Nothing to install.
create_patterns 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_patterns 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_patterns. 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_patterns is provided by the MCPatterns MCP server (nicholasrubright/mcpatterns). 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 →