Low Risk

account_view_account_summary

account_view_account_summary

How to control account_view_account_summary ↓

What account_view_account_summary does on NEAR MCP

AI agents call account_view_account_summary 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.

Low Risk

Why account_view_account_summary needs a policy

The 'view_account_summary' name strongly suggests querying/retrieving account information without modification. This aligns with Read category—no data is created, modified, deleted, or financial actions are performed. Confidence is moderately high despite the empty description because the verb 'view' and context of account summary operations are unambiguous read patterns in blockchain contexts.

From the tool's definition Tool name 'account_view_account_summary' uses 'view' verb, which is a retrieval operation. Server context is 'Interact with the NEAR blockchain' and sibling tools include read operations like account_list_access_keys and account_export_account.

Documented attack patterns abuse exactly the kind of access account_view_account_summary gives an agent:

How to control account_view_account_summary

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 account_view_account_summary:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "account_view_account_summary": {}
  }
}

account_view_account_summary is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NEAR MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about account_view_account_summary

What does the account_view_account_summary tool do? +

account_view_account_summary. It is categorised as a Read tool in the NEAR MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on account_view_account_summary? +

Register the NEAR MCP server in PolicyLayer and add a rule for account_view_account_summary: 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.

What risk level is account_view_account_summary? +

account_view_account_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit account_view_account_summary? +

Yes. Add a rate_limit block to the account_view_account_summary 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.

How do I block account_view_account_summary completely? +

Set action: deny in the PolicyLayer policy for account_view_account_summary. 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.

What MCP server provides account_view_account_summary? +

account_view_account_summary 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.

Enforce policy on every NEAR MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.