get_node

Get node details

Server Pulse Workflow MCP Server pulse-intelligence/pulse-workflow-mcp
Category Read
Risk class Low
Parameters 00 required

What get_node does on Pulse Workflow MCP Server

AI agents call get_node 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.

Why get_node needs a policy

This tool retrieves or queries data about workflow nodes with no side effects. It is a read-only operation consistent with the Read category. Low severity because retrieving node details has minimal blast radius even if misused by an AI agent.

From the tool's definition Tool name 'get_node' with description 'Get node details' indicates a retrieval operation that queries existing node information without modification.

Questions about get_node

What does the get_node tool do? +

Get node details. It is categorised as a Read tool in the Pulse Workflow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_node? +

Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for get_node: 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.

What risk level is get_node? +

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

Can I rate-limit get_node? +

Yes. Add a rate_limit block to the get_node 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_node completely? +

Set action: deny in the PolicyLayer policy for get_node. 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_node? +

get_node 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.