get_compliance_workbench_survey_and_compliance_status
AI agents call get_compliance_workbench_survey_and_compliance_status 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.
This tool appears to query compliance workbench survey data and compliance status from the Omada Identity system. The 'get' verb and governance/audit context suggest read-only retrieval with no side effects.
From the tool's definition Tool name 'get_compliance_workbench_survey_and_compliance_status' uses 'get' prefix, indicating data retrieval.
Attacks that exploit this kind of access
get_compliance_workbench_survey_and_compliance_status. 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_survey_and_compliance_status: 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_survey_and_compliance_status 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_survey_and_compliance_status 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_survey_and_compliance_status. 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_survey_and_compliance_status is provided by the Omada Identity MCP Server MCP server (omadaidentity/omada-mcp-server). 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 →