Execute a write Cypher query on the AGE
AI agents use write-age-cypher to create or update resources in AGE-MCP-Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AGE-MCP-Server environment.
This tool creates or modifies data reversibly through Cypher query execution against an Apache AGE graph database. While 'write' operations can include updates and inserts that are theoretically reversible, the high severity reflects the potential blast radius: an AI agent with unconstrained access could modify critical graph relationships, node properties, or business data at scale.
From the tool's definition Tool name explicitly states 'write-age-cypher' and description confirms 'Execute a write Cypher query'. The tool is designed to modify graph data in PostgreSQL via AGE.
Attacks that exploit this kind of access
Execute a write Cypher query on the AGE. It is categorised as a Write tool in the AGE-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AGE-MCP-Server MCP server in PolicyLayer and add a rule for write-age-cypher: 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 AGE-MCP-Server. Nothing to install.
write-age-cypher 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 write-age-cypher 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 write-age-cypher. 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.
write-age-cypher is provided by the AGE-MCP-Server MCP server (rioriost/age_mcp_server). 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 →