AI agents call baseline_whoami to retrieve information from Baseline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves authentication and authorization metadata about the current session without any side effects. It is a passive information lookup that enables AI agents to understand their current context and permissions, which is typical of read-only diagnostic tools. No data is modified, executed, or destroyed.
From the tool's definition Tool returns session and user information ('logged-in user, access level, current company, and assigned controller ids'). No description indicates modification, deletion, or execution of operations. Server explicitly described as 'read-only interaction'.
Attacks that exploit this kind of access
Validate the session and return the logged-in user, access level, current company, and assigned controller ids. It is categorised as a Read tool in the Baseline MCP Server, which means it retrieves data without modifying state.
Register the Baseline MCP server in PolicyLayer and add a rule for baseline_whoami: 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 Baseline. Nothing to install.
baseline_whoami is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the baseline_whoami 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 baseline_whoami. 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.
baseline_whoami is provided by the Baseline MCP server (swannman/baseline-irrigation-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 →