Store a successful implementation pattern with use cases and context
AI agents use add_pattern to create or update resources in Faulkner DB — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Faulkner DB environment.
This tool creates and persists new implementation pattern records in the knowledge graph. It modifies the underlying data store by adding new entries, which is reversible (patterns can be updated or removed). This is a classic Write operation—it creates structured data without deleting, executing code, or moving financial resources.
From the tool's definition Tool name 'add_pattern' combined with description 'Store a successful implementation pattern' indicates data creation/modification.
Attacks that exploit this kind of access
Store a successful implementation pattern with use cases and context. It is categorised as a Write tool in the Faulkner DB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Faulkner DB MCP server in PolicyLayer and add a rule for add_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 Faulkner DB. Nothing to install.
add_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 add_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 add_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.
add_pattern is provided by the Faulkner DB MCP server (platano78/faulkner-db). 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 →