AI agents call verify to retrieve information from Leafeep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is an authentication/session verification tool. It retrieves or validates account status based on a provided token—a read operation with no side effects. While tokens can be security-sensitive, the tool itself only performs account verification without modifying any data.
From the tool's definition Tool accepts a token parameter ('Paste the token from the login page to connect your account. Usage: verify <token>') to authenticate/verify a user account. No modification of data, no deletion, no code execution, no financial transactions.
Attacks that exploit this kind of access
Paste the token from the login page to connect your account. Usage: verify <token>. It is categorised as a Read tool in the Leafeep MCP Server, which means it retrieves data without modifying state.
Register the Leafeep MCP server in PolicyLayer and add a rule for verify: 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 Leafeep. Nothing to install.
verify 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 verify 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 verify. 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.
verify is provided by the Leafeep MCP server (xhae123/leafeep-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 →