Perform OakVar system checkup to verify installation
AI agents call oakvar_system_check 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.
A system checkup is fundamentally a read operation that gathers diagnostic information about the installation. It has no side effects on data or system configuration—it only reports the current state. This poses minimal risk even if invoked by an AI agent, as it cannot modify, delete, or execute arbitrary operations.
From the tool's definition The tool name 'oakvar_system_check' and description 'Perform OakVar system checkup to verify installation' indicate a diagnostic operation that queries system state without modifying it. It retrieves information about the OakVar installation status.
Attacks that exploit this kind of access
Perform OakVar system checkup to verify installation. 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_system_check: 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_system_check 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_system_check 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_system_check. 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_system_check 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 →