Search past decisions across sessions and roadmap phases
AI agents call search_decisions to retrieve information from Codevira MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical decision data from a persistent knowledge base without creating, modifying, deleting, or executing any actions. It is a pure read operation that gathers context for AI agents. The low severity reflects minimal risk even if misused, as searching decisions cannot directly harm systems or data.
From the tool's definition Tool description states 'Search past decisions across sessions and roadmap phases' — the verb 'search' indicates querying/retrieval with no modification or execution of external operations. No side effects mentioned.
Documented attack patterns abuse exactly the kind of access search_decisions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codevira MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_decisions:
{
"version": "1",
"default": "deny",
"tools": {
"search_decisions": {}
}
}search_decisions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search past decisions across sessions and roadmap phases. It is categorised as a Read tool in the Codevira MCP MCP Server, which means it retrieves data without modifying state.
Register the Codevira MCP server in PolicyLayer and add a rule for search_decisions: 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 Codevira MCP. Nothing to install.
search_decisions 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_decisions 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_decisions. 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_decisions is provided by the Codevira MCP server (sachinshelke/codevira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codevira MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Codevira MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.