Search published documents on lightpaper.org. Returns titles, URLs, authors, quality scores.
AI agents call search_lightpapers to retrieve information from Lightpaper Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about published documents without altering state, executing code, or affecting financial systems. It is a straightforward search/list operation returning public document information.
From the tool's definition Tool description states it "Search published documents" and "Returns titles, URLs, authors, quality scores" - these are read-only retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search published documents on lightpaper.org. Returns titles, URLs, authors, quality scores. It is categorised as a Read tool in the Lightpaper Mcp MCP Server, which means it retrieves data without modifying state.
Register the Lightpaper MCP server in PolicyLayer and add a rule for search_lightpapers: 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 Lightpaper Mcp. Nothing to install.
search_lightpapers 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_lightpapers 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_lightpapers. 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_lightpapers is provided by the Lightpaper MCP server (pypi:lightpaper-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 →