get_workflow_by_name
Get a workflow configuration by its name (exact, case-sensitive match).
This record as markdown: /tools/compliancecow-cow-mcp/get-workflow-by-name.md
What get_workflow_by_name does on ComplianceCow MCP Server
AI agents call get_workflow_by_name 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_workflow_by_name is rated Low
This tool retrieves workflow configuration data by name lookup. It performs a query operation with no capability to modify, delete, or execute actions. The 'Get' verb and read-only nature clearly place it in the Read category with low severity, as it only exposes configuration information without operational impact.
From the tool's definition Tool name is 'get_workflow_by_name' and description states 'Get a workflow configuration by its name' — purely retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_workflow_by_name 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_workflow_by_name, this is the rule to start with:
get_workflow_by_name 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_workflow_by_name call is checked against it from then on.
Questions about get_workflow_by_name
Get a workflow configuration by its name (exact, case-sensitive match). 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_workflow_by_name: 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_workflow_by_name 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_workflow_by_name 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_workflow_by_name. 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_workflow_by_name 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