Searches the Pinako user guide. Returns sections matching the query with title, anchor id, source (
AI agents call search_docs to retrieve information from Pinako AI Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation matching a search query and returns informational results. It has no side effects, creates no resources, executes no code, and cannot be misused to damage data or systems. The blast radius of misuse is minimal—an AI could retrieve irrelevant documentation but cannot harm the system or user data.
From the tool's definition Tool name is 'search_docs' and description states 'Searches the Pinako user guide. Returns sections matching the query' — a classic query/search operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Searches the Pinako user guide. Returns sections matching the query with title, anchor id, source (. It is categorised as a Read tool in the Pinako AI Bridge MCP Server, which means it retrieves data without modifying state.
Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for search_docs: 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 Pinako AI Bridge. Nothing to install.
search_docs 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_docs 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_docs. 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_docs is provided by the Pinako AI Bridge MCP server (teleomorph/pinako-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_docs is one line of Pinako AI Bridge's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →