Get the installed OakVar version
AI agents call oakvar_version to retrieve information from OakVar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve the currently installed version of OakVar. It has no capability to modify data, execute code, delete resources, or affect financial systems. The blast radius of misuse is minimal—an AI agent could only obtain version metadata, which is non-sensitive operational information. This is a straightforward Read category tool with low severity and high confidence.
From the tool's definition Tool name 'oakvar_version' and description 'Get the installed OakVar version' indicate a simple query operation that retrieves version information without modification or side effects.
Attacks that exploit this kind of access
Get the installed OakVar version. It is categorised as a Read tool in the OakVar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OakVar MCP Server MCP server in PolicyLayer and add a rule for oakvar_version: 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 OakVar MCP Server. Nothing to install.
oakvar_version 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 oakvar_version 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 oakvar_version. 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.
oakvar_version is provided by the OakVar MCP Server MCP server (miliyarsh/oakvar-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 →