List supported workflows and current model versions (GET /v1/workflows).
AI agents call list_workflows to retrieve information from Sentinel Signal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available workflows and model versions without modifying, deleting, or executing any operations. It is a straightforward read operation that returns informational data only.
From the tool's definition Tool name is 'list_workflows' and description states 'List supported workflows' with GET HTTP method, indicating a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List supported workflows and current model versions (GET /v1/workflows). It is categorised as a Read tool in the Sentinel Signal MCP MCP Server, which means it retrieves data without modifying state.
Register the Sentinel Signal MCP server in PolicyLayer and add a rule for list_workflows: 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 Sentinel Signal MCP. Nothing to install.
list_workflows 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 list_workflows 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 list_workflows. 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.
list_workflows is provided by the Sentinel Signal MCP server (sentinelsignal/sentinel-signal-mcp). 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 →