contract_view_functions
AI agents call contract_view_functions 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.
The tool appears to retrieve or query contract function metadata from the NEAR blockchain. The 'view' prefix in NEAR contracts designates state-read operations that cannot alter on-chain data. Even though the description is empty, the naming convention is a standard blockchain pattern where 'view' functions are immutable queries. This fits the Read category.
From the tool's definition Tool name 'contract_view_functions' strongly implies read-only querying of contract functions. The word 'view' in blockchain contexts universally denotes read-only operations that do not modify state. No description provided to contradict this inference.
Documented attack patterns abuse exactly the kind of access contract_view_functions 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_view_functions:
{
"version": "1",
"default": "deny",
"tools": {
"contract_view_functions": {}
}
}contract_view_functions 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_view_functions. 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_view_functions: 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_view_functions 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_view_functions 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_view_functions. 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_view_functions 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.