add_parameter
AI agents use add_parameter 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.
Adding a parameter to a function/method modifies code structure reversibly (it can be removed or edited later). This is a Write operation—it creates or modifies code without deleting it irreversibly. High severity because injecting incorrect or malicious parameters could alter function signatures, introduce type errors, or change behavior in unexpected ways.
From the tool's definition Tool name is 'add_parameter' with empty description. Sibling tools include 'add_field', 'add_method', 'add_import', 'add_key', 'delete_symbol', etc., confirming this server performs structural code modifications.
Attacks that exploit this kind of access
add_parameter. 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.
Register the Ast Editor MCP server in PolicyLayer and add a rule for add_parameter: 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.
add_parameter 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_parameter 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_parameter. 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_parameter 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.
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 →