List configured federation nodes in an orchestrator project
AI agents call storybloq_node_list to retrieve information from Storybloq 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 state of federation nodes in a project. It performs no modifications, deletions, executions, or financial transactions. The action is passive information retrieval, fitting the Read category.
From the tool's definition Tool name 'list' and description 'List configured federation nodes' indicate retrieval of existing configuration data without modification or side effects.
Documented attack patterns abuse exactly the kind of access storybloq_node_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Storybloq, and nothing reaches the server without passing your rules. This is the rule we recommend for storybloq_node_list:
{
"version": "1",
"default": "deny",
"tools": {
"storybloq_node_list": {}
}
}storybloq_node_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List configured federation nodes in an orchestrator project. It is categorised as a Read tool in the Storybloq MCP Server, which means it retrieves data without modifying state.
Register the Storybloq MCP server in PolicyLayer and add a rule for storybloq_node_list: 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 Storybloq. Nothing to install.
storybloq_node_list 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 storybloq_node_list 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 storybloq_node_list. 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.
storybloq_node_list is provided by the Storybloq MCP server (storybloq/storybloq). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 Storybloq tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 Storybloq tools catalogued and risk-classified — across an index of 42,500+ MCP servers.