AI agents invoke lexicon_raw_request to trigger actions in Lexicon. 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 allows arbitrary HTTP requests to any /v1 API path, meaning it can trigger any operation the Lexicon API supports — reads, writes, or destructive actions — depending on the arguments passed. It is not constrained to read-only operations, so Execute is the most appropriate category given its open-ended nature.
From the tool's definition Call any Lexicon /v1 path with JSON body
Attacks that exploit this kind of access
Deprecated: use lexicon_request with method GET. Call any Lexicon /v1 path with JSON body. It is categorised as a Execute tool in the Lexicon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lexicon MCP server in PolicyLayer and add a rule for lexicon_raw_request: 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_raw_request 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 lexicon_raw_request 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_raw_request. 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_raw_request 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 →