get_workflow_by_name

Get a workflow configuration by its name (exact, case-sensitive match).

SERVERComplianceCow MCP Server SOURCEcompliancecow/cow-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about get_workflow_by_name

What does the get_workflow_by_name tool do? +

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.

How do I enforce a policy on get_workflow_by_name? +

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.

What risk level is get_workflow_by_name? +

get_workflow_by_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workflow_by_name? +

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.

How do I block get_workflow_by_name completely? +

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.

What MCP server provides get_workflow_by_name? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ComplianceCow MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.