AI agents call get_session_context 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.
The tool performs a read operation to fetch session context information. There is no indication of side effects, data modification, or destructive actions. The low severity reflects that retrieving context data poses minimal risk even if misused by an agent, as it only accesses existing information.
From the tool's definition Tool name 'get_session_context' indicates retrieval of session context data. Description is minimal ('Single'), but the verb 'get' combined with the server's stated purpose of 'maintaining a shared knowledge base' and 'automated context tracking' suggests…
Documented attack patterns abuse exactly the kind of access get_session_context 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 get_session_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_context": {}
}
}get_session_context 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.
Single. 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 get_session_context: 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.
get_session_context 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 get_session_context 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 get_session_context. 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.
get_session_context 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.