Design a half-wave dipole antenna. Classic resonant antenna with well-known characteristics.
AI agents use openems_create_dipole to create or update resources in Mcp Openems — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Openems environment.
This tool creates/generates a dipole antenna design configuration. It produces output (a design artifact or script) but does not execute simulations, delete data, or involve financial transactions. It is a Write operation as it creates a new design structure, with low severity since it only generates design data with no destructive or financial side effects.
From the tool's definition 'Design a half-wave dipole antenna' — creates an antenna design/structure
Attacks that exploit this kind of access
Design a half-wave dipole antenna. Classic resonant antenna with well-known characteristics. It is categorised as a Write tool in the Mcp Openems MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Openems MCP server in PolicyLayer and add a rule for openems_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 Openems. Nothing to install.
openems_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 openems_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 openems_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.
openems_create_dipole is provided by the Mcp Openems MCP server (rfingadam/mcp-openems). 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 →