contract_get_function_args
AI agents call contract_get_function_args to retrieve information from NEAR MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
With no description provided, confidence is reduced, but the naming convention ('get_function_args') strongly indicates a data retrieval operation for querying contract metadata. This has no side effects and does not modify state, execute code, or transfer value. It falls into the Read category with low severity since exposing contract interface information poses minimal direct risk.
From the tool's definition Tool name 'contract_get_function_args' and the pattern of sibling tools suggest this retrieves contract function argument metadata or schema information from the NEAR blockchain. The 'get' prefix indicates a read operation.
Documented attack patterns abuse exactly the kind of access contract_get_function_args gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NEAR MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for contract_get_function_args:
{
"version": "1",
"default": "deny",
"tools": {
"contract_get_function_args": {}
}
}contract_get_function_args 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.
contract_get_function_args. It is categorised as a Read tool in the NEAR MCP MCP Server, which means it retrieves data without modifying state.
Register the NEAR MCP server in PolicyLayer and add a rule for contract_get_function_args: 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 NEAR MCP. Nothing to install.
contract_get_function_args 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 contract_get_function_args 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 contract_get_function_args. 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.
contract_get_function_args is provided by the NEAR MCP server (nearai/near-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NEAR MCP, 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.
23 NEAR MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.