get_compliance_workbench_data
AI agents call get_compliance_workbench_data 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 tool retrieves compliance data from a workbench, which is a query/read operation. While the empty description reduces confidence, the naming convention and server context (identity governance and compliance monitoring) suggest it queries compliance status rather than modifies, executes, or deletes.
From the tool's definition Tool name 'get_compliance_workbench_data' uses 'get' prefix, indicating data retrieval with no side effects.
Attacks that exploit this kind of access
get_compliance_workbench_data. 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_compliance_workbench_data: 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_compliance_workbench_data 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_compliance_workbench_data 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_compliance_workbench_data. 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_compliance_workbench_data 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 →