Run NEC2 simulation on an antenna to get impedance and radiation pattern.
AI agents invoke nec2_simulate to trigger actions in Mcp Nec2 Antenna. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes external code (the NEC2 electromagnetic simulation engine) and produces computed results based on input parameters. It is Execute rather than Read because it runs a simulator with side effects (resource consumption, computation) rather than merely querying stored data.
From the tool's definition Tool performs 'Run NEC2 simulation' which triggers external computational operations (the NEC2 method-of-moments solver) whose effects depend on antenna configuration arguments passed to it.
Attacks that exploit this kind of access
Run NEC2 simulation on an antenna to get impedance and radiation pattern. It is categorised as a Execute tool in the Mcp Nec2 Antenna MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Nec2 Antenna MCP server in PolicyLayer and add a rule for nec2_simulate: 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_simulate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the nec2_simulate 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_simulate. 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_simulate 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 →