search_explain
AI agents call search_explain to retrieve information from Vector Task MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to search and explain results within the vector task management system. As a search function with no indication of data modification or external effects, it falls under Read operations. Low severity because search operations have minimal blast radius—worst case returns incorrect information without data loss or state changes.
From the tool's definition Tool name 'search_explain' and server context indicate retrieval/query functionality with semantic search capabilities.
Attacks that exploit this kind of access
search_explain. It is categorised as a Read tool in the Vector Task MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vector Task MCP Server MCP server in PolicyLayer and add a rule for search_explain: 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 Vector Task MCP Server. Nothing to install.
search_explain 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_explain 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_explain. 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_explain is provided by the Vector Task MCP Server MCP server (xsaven/vector-task-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 →