jm_graph_build
Build or rebuild the resource graph with a net sleep interval.
This record as markdown: /tools/io-github-iowarp-adios-mcp/jm-graph-build.md
What jm_graph_build does on CLIO Adios
AI agents invoke jm_graph_build to trigger actions in CLIO Adios. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why jm_graph_build is rated High
This tool triggers execution of a resource graph construction/rebuilding process with configurable timing parameters. While it does not permanently delete data (not Destructive) or move money (not Financial), it executes code that modifies computational resource state and scheduling, which could have unintended side effects if parameters are misconfigured by an AI agent.
From the tool's definition Tool description: 'Build or rebuild the resource graph with a net sleep interval.' The verbs 'build' and 'rebuild' indicate execution of a graph construction operation that modifies system resource state, and 'sleep interval' parameter suggests control over…
Attacks that exploit this kind of access
The rule that runs jm_graph_build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jm_graph_build, this is the rule to start with:
jm_graph_build stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every jm_graph_build call is checked against it from then on.
Questions about jm_graph_build
Build or rebuild the resource graph with a net sleep interval. It is categorised as a Execute tool in the CLIO Adios MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for jm_graph_build: 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 CLIO Adios. Nothing to install.
jm_graph_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jm_graph_build 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 jm_graph_build. 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.
jm_graph_build is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CLIO Adios, and thousands of servers like it.
Across the catalogue