AI agents use create_cursor_rules to create or update resources in Memory Bank MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory Bank MCP environment.
This tool creates new data entries (cursor rules) within the memory bank system, making it a Write operation. It is reversible via update or delete operations, so not Destructive.
From the tool's definition Tool name 'create_cursor_rules' combined with context of a memory bank documentation system suggests creating or adding new cursor rules/configuration entries.
Documented attack patterns abuse exactly the kind of access create_cursor_rules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Bank MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_cursor_rules:
{
"version": "1",
"default": "deny",
"tools": {
"create_cursor_rules": {
"limits": [
{
"counter": "create_cursor_rules_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_cursor_rules 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.
Free to start. No card required.
create_cursor_rules. It is categorised as a Write tool in the Memory Bank MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory Bank MCP server in PolicyLayer and add a rule for create_cursor_rules: 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 Memory Bank MCP. Nothing to install.
create_cursor_rules 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_cursor_rules 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_cursor_rules. 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_cursor_rules is provided by the Memory Bank MCP server (tuncer-byte/memory-bank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Memory Bank MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Memory Bank MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.