truenas_api_call
Make a raw API call to any TrueNAS endpoint not covered by specific tools. This is an escape hatch for advanced or uncommon operations. The body parameter accepts a JSON string that will be parsed before sending.
This record as markdown: /tools/spranab-truenas-mcp/truenas-api-call.md
What truenas_api_call does on Truenas
AI agents invoke truenas_api_call to trigger actions in Truenas. 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 truenas_api_call is rated High
This tool allows arbitrary API calls to any TrueNAS endpoint, making it a universal escape hatch with no restrictions. It can trigger destructive operations (delete, drop, wipe), financial actions, writes, or any system-level command depending on the endpoint and body supplied.
From the tool's definition 'Make a raw API call to any TrueNAS endpoint not covered by specific tools. This is an escape hatch for advanced or uncommon operations.'
Attacks that exploit this kind of access
The rule that runs truenas_api_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For truenas_api_call, this is the rule to start with:
truenas_api_call 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 Truenas, apply this rule, and every truenas_api_call call is checked against it from then on.
Questions about truenas_api_call
Make a raw API call to any TrueNAS endpoint not covered by specific tools. This is an escape hatch for advanced or uncommon operations. The body parameter accepts a JSON string that will be parsed before sending. It is categorised as a Execute tool in the Truenas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Truenas MCP server in PolicyLayer and add a rule for truenas_api_call: 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 Truenas. Nothing to install.
truenas_api_call 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 truenas_api_call 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 truenas_api_call. 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.
truenas_api_call is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
Across the catalogue