REQUIRED before configuring a node. Get config schema for node type.
AI agents call get_node_schema 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 configuration schema metadata for a node type. It has no side effects, does not modify any state, and is purely informational retrieval. It falls squarely into the Read category. Severity is low because schema retrieval poses minimal risk even if misused by an agent — it cannot modify workflows, execute code, or cause data loss.
From the tool's definition Tool name is 'get_node_schema' and description states 'Get config schema for node type' — this retrieves schema information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
REQUIRED before configuring a node. Get config schema for node type. 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 get_node_schema: 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.
get_node_schema 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 get_node_schema 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 get_node_schema. 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.
get_node_schema 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 →