AI agents use hfss_assign_wave_port to create or update resources in HFSS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HFSS MCP Server environment.
Assigning a wave port modifies simulation setup by adding or updating a boundary condition, which is a data structure change within the ANSYS HFSS model. This is reversible (can be reassigned or removed) and does not execute arbitrary code or delete data, so it falls under Write rather than Execute.
From the tool's definition The tool performs assignment of a wave port to a face, which is a creation or modification of a simulation boundary condition. The verb 'assign' indicates a reversible configuration change to the HFSS project.
Documented attack patterns abuse exactly the kind of access hfss_assign_wave_port gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HFSS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for hfss_assign_wave_port:
{
"version": "1",
"default": "deny",
"tools": {
"hfss_assign_wave_port": {
"limits": [
{
"counter": "hfss_assign_wave_port_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}hfss_assign_wave_port stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Assign a wave port to a face. It is categorised as a Write tool in the HFSS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HFSS MCP Server MCP server in PolicyLayer and add a rule for hfss_assign_wave_port: 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 HFSS MCP Server. Nothing to install.
hfss_assign_wave_port 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 hfss_assign_wave_port 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 hfss_assign_wave_port. 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.
hfss_assign_wave_port is provided by the HFSS MCP Server MCP server (leonardwy/hfss_mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HFSS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 HFSS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.