Navigates to the PIM (Personal Information Management) page using the left-hand navigation menu. Assumes user is already logged in.
AI agents invoke navigate_to_pim to trigger actions in MCP Login 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.
This tool executes a navigation action in a browser, which is an external operation that modifies browser state and may trigger page loads or application logic. While navigation alone is not inherently destructive, it falls under Execute category as it performs an action on an external system (the browser/web application) whose consequences depend on what the user does next.
From the tool's definition Tool description states it 'navigates to the PIM page using the left-hand navigation menu', indicating it performs browser navigation actions.
Attacks that exploit this kind of access
Navigates to the PIM (Personal Information Management) page using the left-hand navigation menu. Assumes user is already logged in. It is categorised as a Execute tool in the MCP Login Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Login Server MCP server in PolicyLayer and add a rule for navigate_to_pim: 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 Login Server. Nothing to install.
navigate_to_pim 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 navigate_to_pim 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 navigate_to_pim. 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.
navigate_to_pim is provided by the MCP Login Server MCP server (nieperdragon/custom_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 →