add_key

add_key

Server Ast Editor kambleakash0/ast-editor
Category Write
Risk class Medium
Parameters 00 required

What add_key does on Ast Editor

AI agents use add_key to create or update resources in Ast Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ast Editor environment.

Why add_key needs a policy

This tool creates or modifies code structure by adding a key, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or handle financial operations.

From the tool's definition Tool name 'add_key' with sibling tools like 'add_field', 'add_import', 'add_method', 'add_parameter', 'add_top_level', and 'append_to_array' indicates structural code modification.

Questions about add_key

What does the add_key tool do? +

add_key. It is categorised as a Write tool in the Ast Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_key? +

Register the Ast Editor MCP server in PolicyLayer and add a rule for add_key: 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 Ast Editor. Nothing to install.

What risk level is add_key? +

add_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_key? +

Yes. Add a rate_limit block to the add_key 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.

How do I block add_key completely? +

Set action: deny in the PolicyLayer policy for add_key. 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.

What MCP server provides add_key? +

add_key is provided by the Ast Editor MCP server (kambleakash0/ast-editor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.