AI agents use generate-code to create or update resources in Neosql — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neosql environment.
Code generation is a Write operation—it creates new data (code) that is reversible and has no immediate destructive or financial impact. However, the vague description ('under development') and lack of specifics about what code is generated, where it's stored, or how it's deployed create uncertainty.
From the tool's definition Tool name 'generate-code' and description stating it generates code. As a code generation tool, it would create new code artifacts (Write category). Description is minimal ('under development'), limiting confidence.
Attacks that exploit this kind of access
Generate Code is under development. It is categorised as a Write tool in the Neosql MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neosql MCP server in PolicyLayer and add a rule for generate-code: 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 Neosql. Nothing to install.
generate-code 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 generate-code 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 generate-code. 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.
generate-code is provided by the Neosql MCP server (unvus/neosql-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 →