REQUIRED before add_node. Lists available node types.
AI agents call list_node_types 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 queries and returns information about available node types in the Pulse workflow system. It performs no modifications, deletions, or triggering of external operations. It is a straightforward data retrieval operation used to inform subsequent workflow creation steps, placing it firmly in the Read category with low severity.
From the tool's definition Tool name is 'list_node_types' and description states it 'Lists available node types' — a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
REQUIRED before add_node. Lists available node types. 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 list_node_types: 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.
list_node_types 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_node_types 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_node_types. 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_node_types 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 →