List edges. Returns: [{id, source, target}]
AI agents call list_edges 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 workflow edge (connection) metadata in a read-only fashion. There are no side effects, no data creation, modification, or deletion, and no code execution or financial impact. It falls squarely into the Read category with low severity since querying workflow structure poses minimal risk to the system.
From the tool's definition Tool name is 'list_edges' and description states 'List edges. Returns: [{id, source, target}]' — a pure query operation that retrieves and returns data about workflow connections without modification.
Attacks that exploit this kind of access
List edges. Returns: [{id, 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 list_edges: 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_edges 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_edges 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_edges. 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_edges 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 →