v3.1.0 M2: Top-K live working-memory entries by decay score
AI agents call working_get 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 ranked working-memory entries without side effects. It fits the Read category pattern (query, fetch, list). The blast radius is minimal—misuse would return unwanted data but cannot modify, delete, or execute code.
From the tool's definition Tool name 'working_get' and description 'Top-K live working-memory entries by decay score' indicate retrieval of entries from working memory with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access working_get 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 working_get:
{
"version": "1",
"default": "deny",
"tools": {
"working_get": {}
}
}working_get 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.
v3.1.0 M2: Top-K live working-memory entries by decay score. 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 working_get: 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.
working_get 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 working_get 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 working_get. 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.
working_get 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.