AXIS-owned BM25 search engine over the corpus YOUR account has indexed. NOT a Google/Bing scraper — agents build their own searchable index by first calling operation=
AI agents call iliad_web_search to retrieve information from AXIS iliad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from a pre-built search index owned by the user's account. It has no side effects, does not modify data, and does not execute external operations. It is purely informational retrieval, fitting the 'Read' category. The restriction to 'YOUR account has indexed' further suggests it operates only on user-controlled indexed data without destructive or mutative capabilities.
From the tool's definition Tool is described as a 'search engine' that performs queries over an indexed corpus. The phrase 'agents build their own searchable index by first calling operation=' indicates this is a retrieval operation that searches pre-indexed data without modifying it.
Attacks that exploit this kind of access
AXIS-owned BM25 search engine over the corpus YOUR account has indexed. NOT a Google/Bing scraper — agents build their own searchable index by first calling operation=. It is categorised as a Read tool in the AXIS iliad MCP Server, which means it retrieves data without modifying state.
Register the AXIS iliad MCP server in PolicyLayer and add a rule for iliad_web_search: 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 AXIS iliad. Nothing to install.
iliad_web_search 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 iliad_web_search 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 iliad_web_search. 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.
iliad_web_search is provided by the AXIS iliad MCP server (lastmanupinc-hub/axis-iliad). 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 →