search_by_tags
AI agents call search_by_tags to retrieve information from FastMCP Document Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are read-only queries that retrieve and filter existing data without side effects. No modification, deletion, or execution of code is implied. The empty description reduces confidence slightly, but the clear naming pattern ('search_*') and sibling tool naming conventions (list_documents, get_document, get_sentiment) establish this as a retrieval operation.
From the tool's definition Tool name 'search_by_tags' indicates a search operation that retrieves documents by their tags. Server context shows this is a document analysis and management tool.
Attacks that exploit this kind of access
search_by_tags. It is categorised as a Read tool in the FastMCP Document Analyzer MCP Server, which means it retrieves data without modifying state.
Register the FastMCP Document Analyzer MCP server in PolicyLayer and add a rule for search_by_tags: 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 FastMCP Document Analyzer. Nothing to install.
search_by_tags 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_by_tags 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_by_tags. 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_by_tags is provided by the FastMCP Document Analyzer MCP server (tathagat017/document-analyser-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 →