Search a LibreTexts library. Returns title + path + uri for each hit.
AI agents call search to retrieve information from Libretexts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward search/query operation that retrieves and returns information about LibreTexts library contents. It performs no write, execute, destructive, or financial operations. The returned data (title, path, uri) are informational metadata. Low severity because misuse would only result in unintended searches, with no harmful effects to systems or data.
From the tool's definition Tool description explicitly states it 'Search[es] a LibreTexts library. Returns title + path + uri for each hit.' The verb 'search' combined with returning metadata (title, path, uri) indicates a read-only query operation with no modifications or side effects.
Attacks that exploit this kind of access
Search a LibreTexts library. Returns title + path + uri for each hit. It is categorised as a Read tool in the Libretexts MCP Server, which means it retrieves data without modifying state.
Register the Libretexts MCP server in PolicyLayer and add a rule for 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 Libretexts. Nothing to install.
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 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 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.
search is provided by the Libretexts MCP server (mubashir1osmani/libretexts-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 →