AI agents call lexicon_ping to retrieve information from Lexicon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Pinging an API endpoint to verify it is online and responsive is a read-only operation that queries connectivity status without retrieving, modifying, or executing any meaningful actions on the Lexicon library. The blast radius if misused is minimal—at worst it generates unnecessary network traffic. This aligns with the Read category (queries/checks with no side effects).
From the tool's definition Tool is described as checking if the Lexicon Local API is reachable. This is a diagnostic/health-check operation with no data retrieval, modification, or side effects beyond confirming connectivity status.
Attacks that exploit this kind of access
Check Lexicon Local API is reachable (Lexicon app must be running with API enabled under Settings → Integrations). It is categorised as a Read tool in the Lexicon MCP Server, which means it retrieves data without modifying state.
Register the Lexicon MCP server in PolicyLayer and add a rule for lexicon_ping: 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 Lexicon. Nothing to install.
lexicon_ping 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 lexicon_ping 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 lexicon_ping. 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.
lexicon_ping is provided by the Lexicon MCP server (turbotailz/lexicon-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 →