Clear in-memory metadata/query cache. Optionally provide a tool name prefix.
AI agents call clear_cache to permanently remove resources in OpenLink MCP Server for ODBC — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache irreversibly destroys in-memory data (metadata and query results). While the underlying source data is unaffected, the cached information is permanently lost and cannot be undone. This fits the Destructive category. Severity is medium because the blast radius is limited to performance impact (cache misses, re-query overhead) rather than loss of persistent data.
From the tool's definition 'Clear in-memory metadata/query cache' — clearing cache is an irreversible operation that destroys cached data that cannot be recovered
Attacks that exploit this kind of access
Clear in-memory metadata/query cache. Optionally provide a tool name prefix. It is categorised as a Destructive tool in the OpenLink MCP Server for ODBC MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenLink MCP Server for ODBC MCP server in PolicyLayer and add a rule for clear_cache: 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 OpenLink MCP Server for ODBC. Nothing to install.
clear_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_cache 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 clear_cache. 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.
clear_cache is provided by the OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-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 →