AI agents call get_nodit_api_spec to retrieve information from Nodit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
operationId | string | Yes | The operationId to get the resolved specification for. Must include the chain prefix in `{chain}-{methodName}` format (e.g., 'ethereum-eth_blocknumber', 'aptos- |
Parameters from the server's own tool schema.
This tool retrieves specification metadata for a blockchain context API operationId and returns it as read-only JSON data. It performs no creation, modification, deletion, or execution of external operations—merely fetching and returning existing specification information.
From the tool's definition Operates on an API specification retrieval with 'Gets the fully resolved spec details' and 'Returns details as a JSON string', which are query/read operations with no side effects.
Attacks that exploit this kind of access
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, which means it retrieves data without modifying state.
get_nodit_api_spec accepts 1 parameter: operationId. Required: operationId. The full parameter table on this page comes from the server's own tool schema.
Register the Nodit 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. 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 (@noditlabs/nodit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →