This function calls a specific Nodit Blockchain Context API using its operationId. Before making the call, it
AI agents invoke call_nodit_api to trigger actions in Nodit MCP Server. 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.
The tool is a generic API dispatcher that can trigger any operation available in the Nodit API catalogue. While many of those operations may be read-only blockchain queries, the tool itself is an execution primitive whose side effects are fully determined by the operationId argument. This spans potentially read, write, or destructive operations, so the most severe applicable category is Execute.
From the tool's definition 'calls a specific Nodit Blockchain Context API using its operationId' — this tool executes arbitrary API operations identified by operationId, meaning the actual effect depends entirely on which operation is invoked
Documented attack patterns abuse exactly the kind of access call_nodit_api gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nodit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for call_nodit_api:
{
"version": "1",
"default": "deny",
"tools": {
"call_nodit_api": {
"limits": [
{
"counter": "call_nodit_api_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}call_nodit_api 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.
Free to start. No card required.
This function calls a specific Nodit Blockchain Context API using its operationId. Before making the call, it. It is categorised as a Execute tool in the Nodit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nodit MCP Server MCP server in PolicyLayer and add a rule for call_nodit_api: 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 Nodit MCP Server. Nothing to install.
call_nodit_api 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 call_nodit_api 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 call_nodit_api. 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.
call_nodit_api is provided by the Nodit MCP Server MCP server (noditlabs/nodit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nodit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Nodit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.