get_cache_efficiency
AI agents call get_cache_efficiency to retrieve information from Omada Identity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name indicates a retrieval operation ('get_') focused on monitoring cache efficiency metrics. No description is provided, but the naming pattern and context of sibling tools (get_cache_stats, get_access_requests, get_all_omada_identities) suggest this is a read-only query of internal system metrics. There is no indication of data modification, deletion, code execution, or financial impact.
From the tool's definition Tool name 'get_cache_efficiency' with empty description; based on naming convention and sibling tools like 'get_cache_stats', this retrieves cache performance metrics without modifying state.
Attacks that exploit this kind of access
get_cache_efficiency. It is categorised as a Read tool in the Omada Identity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Omada Identity MCP Server MCP server in PolicyLayer and add a rule for get_cache_efficiency: 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 Omada Identity MCP Server. Nothing to install.
get_cache_efficiency 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_cache_efficiency 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_cache_efficiency. 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_cache_efficiency is provided by the Omada Identity MCP Server MCP server (walkerpauldavid/omadaidentitymcpserver). 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 →