Navigate platform sections
AI agents invoke arcas_onlineeda_navigate to trigger actions in Arcas OnlineEDA MCP Server. 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.
While 'navigate' alone could suggest simple Read operations (viewing different sections), the context of an EDA platform with verification, file upload, and project management capabilities suggests that navigation may trigger automated workflows or state transitions.
From the tool's definition Tool navigates platform sections, which implies triggering state changes or interactions within the Arcas OnlineEDA platform.
Attacks that exploit this kind of access
Navigate platform sections. It is categorised as a Execute tool in the Arcas OnlineEDA MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Arcas OnlineEDA MCP Server MCP server in PolicyLayer and add a rule for arcas_onlineeda_navigate: 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 Arcas OnlineEDA MCP Server. Nothing to install.
arcas_onlineeda_navigate 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 arcas_onlineeda_navigate 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 arcas_onlineeda_navigate. 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.
arcas_onlineeda_navigate is provided by the Arcas OnlineEDA MCP Server MCP server (ssql2014/arcas-onlineeda-mcp). 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 →