AI agents call jis_whoami to retrieve information from Jis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the current user's identity configuration. It performs a read-only operation with no side effects, simply showing existing identity information or setup instructions if not configured.
From the tool's definition Show your current JIS identity
Attacks that exploit this kind of access
Show your current JIS identity (jis:). If not configured, shows how to set one up. It is categorised as a Read tool in the Jis MCP Server, which means it retrieves data without modifying state.
Register the Jis MCP server in PolicyLayer and add a rule for jis_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 Jis. Nothing to install.
jis_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 jis_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 jis_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.
jis_whoami is provided by the Jis MCP server (jaspertvdm/mcp-server-jis). 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 →