List installed and/or available OakVar modules
AI agents call oakvar_module_list 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 is a straightforward informational tool that enumerates modules. It has no side effects, does not modify state, does not execute code or trigger operations, and does not delete or create resources. It falls squarely into the Read category with low severity because misuse by an AI agent would only expose metadata about available modules, posing minimal risk.
From the tool's definition Tool name and description indicate 'List installed and/or available OakVar modules'—a query operation that retrieves information about module availability and installation status without modifying or executing anything.
Attacks that exploit this kind of access
List installed and/or available OakVar modules. 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_module_list: 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_module_list 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_module_list 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_module_list. 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_module_list 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 →