Create a half-wave dipole antenna. Returns antenna ID for simulation.
AI agents use nec2_create_dipole to create or update resources in Mcp Nec2 Antenna — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Nec2 Antenna environment.
This tool creates a new antenna design object (reversible data creation) without executing simulations, deleting data, or moving resources. The created antenna configuration can be modified or deleted later. While it prepares for Execute-category simulation, the tool itself only performs Write operations.
From the tool's definition Tool description states "Create a half-wave dipole antenna. Returns antenna ID for simulation." The verb "Create" indicates data creation; the tool generates and stores a new antenna configuration artifact.
Attacks that exploit this kind of access
Create a half-wave dipole antenna. Returns antenna ID for simulation. It is categorised as a Write tool in the Mcp Nec2 Antenna MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Nec2 Antenna MCP server in PolicyLayer and add a rule for nec2_create_dipole: 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 Mcp Nec2 Antenna. Nothing to install.
nec2_create_dipole 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 nec2_create_dipole 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 nec2_create_dipole. 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.
nec2_create_dipole is provided by the Mcp Nec2 Antenna MCP server (rfingadam/mcp-nec2-antenna). 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 →