View workflow structure. Returns: {nodes:[{id,type,title}], edges:[{source,target}]}
AI agents call view_workflow to retrieve information from Pulse Workflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the structure of a workflow (nodes and edges) without creating, modifying, deleting, or executing anything. It is a straightforward read operation with no side effects, matching the Read category definition.
From the tool's definition Tool name 'view_workflow' and description 'View workflow structure' indicate retrieval of workflow data with no modifications. Returns structured node and edge information only.
Attacks that exploit this kind of access
View workflow structure. Returns: {nodes:[{id,type,title}], edges:[{source,target}]}. It is categorised as a Read tool in the Pulse Workflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for view_workflow: 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 Pulse Workflow MCP Server. Nothing to install.
view_workflow 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 view_workflow 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 view_workflow. 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.
view_workflow is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-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 →