Gets the fully resolved spec details for a Nodit Blockchain Context API operationId. Returns details as a JSON string.
AI agents call get_nodit_api_spec to retrieve information from Nodit 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 and returns specification metadata about API operations—it queries information without modifying, creating, deleting, or executing any blockchain operations. The returned JSON spec is informational only. It fits the Read category profile: retrieves data with no side effects. No financial risk, no code execution, no destructive capability.
From the tool's definition Tool description states it 'Gets the fully resolved spec details for a Nodit Blockchain Context API operationId.
Documented attack patterns abuse exactly the kind of access get_nodit_api_spec 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 get_nodit_api_spec:
{
"version": "1",
"default": "deny",
"tools": {
"get_nodit_api_spec": {}
}
} get_nodit_api_spec 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.
Gets the fully resolved spec details for a Nodit Blockchain Context API operationId. Returns details as a JSON string. It is categorised as a Read tool in the Nodit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nodit MCP Server MCP server in PolicyLayer and add a rule for get_nodit_api_spec: 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.
get_nodit_api_spec 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 get_nodit_api_spec 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 get_nodit_api_spec. 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.
get_nodit_api_spec 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.