get_dashboard_common_controls_details
A read tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/get-dashboard-common-controls-details.md
What get_dashboard_common_controls_details does on ComplianceCow MCP Server
AI agents call get_dashboard_common_controls_details to retrieve information from ComplianceCow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dashboard_common_controls_details is rated Low
This tool retrieves dashboard data about common controls without modifying, deleting, or executing operations. While the description is empty, the name and server context strongly indicate a read-only query operation. Confidence is slightly reduced due to missing direct tool description, but the naming pattern and server purpose make misuse risk low even if an AI agent were to invoke it with arbitrary parameters.
From the tool's definition Tool name contains 'get_dashboard' and 'details', indicating data retrieval. Server description confirms it 'retrieve[s] compliance insights, dashboard data, and auditable evidence through a Compliance Graph.' No write, execute, delete, or financial…
Attacks that exploit this kind of access
The rule that runs get_dashboard_common_controls_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ComplianceCow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dashboard_common_controls_details, this is the rule to start with:
get_dashboard_common_controls_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ComplianceCow MCP Server, apply this rule, and every get_dashboard_common_controls_details call is checked against it from then on.
Questions about get_dashboard_common_controls_details
get_dashboard_common_controls_details is a read tool on the ComplianceCow MCP Server MCP server. It is categorised as a Read tool in the ComplianceCow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ComplianceCow MCP Server MCP server in PolicyLayer and add a rule for get_dashboard_common_controls_details: 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 ComplianceCow MCP Server. Nothing to install.
get_dashboard_common_controls_details 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_dashboard_common_controls_details 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_dashboard_common_controls_details. 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_dashboard_common_controls_details is provided by the ComplianceCow MCP Server MCP server (compliancecow/cow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ComplianceCow MCP Server, and thousands of servers like it.
This server
Across the catalogue