search_guidelines
AI agents call search_guidelines to retrieve information from Glanser Guidelines MCP Server 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 guidelines data without side effects. It performs a search operation over a static guidelines corpus, consistent with Read category tools. The empty description and presence of similar read-only tools on the server reinforce that this is a data retrieval function.
From the tool's definition Tool name 'search_guidelines' combined with server description stating 'semantic search over a team's coding guidelines corpus' and sibling tools like 'get_by_scope', 'get_section', 'list_documents', 'list_sections' all indicate read-only query operations.
Attacks that exploit this kind of access
search_guidelines. It is categorised as a Read tool in the Glanser Guidelines MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Glanser Guidelines MCP Server MCP server in PolicyLayer and add a rule for search_guidelines: 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 Glanser Guidelines MCP Server. Nothing to install.
search_guidelines 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_guidelines 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_guidelines. 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_guidelines is provided by the Glanser Guidelines MCP Server MCP server (vbridge7/mcp-server). 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 →