system_import_account
AI agents use system_import_account to create or update resources in NEAR MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NEAR MCP environment.
The tool performs account import on the NEAR blockchain, which creates or modifies account data reversibly—classifying it as Write rather than Execute. While the description is empty (lowering confidence slightly), the name and server context are clear.
From the tool's definition Tool name 'system_import_account' on a blockchain interaction server (NEAR MCP) indicates account import functionality.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_import_account 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 system_import_account:
{
"version": "1",
"default": "deny",
"tools": {
"system_import_account": {
"limits": [
{
"counter": "system_import_account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}system_import_account stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
system_import_account. It is categorised as a Write tool in the NEAR MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NEAR MCP server in PolicyLayer and add a rule for system_import_account: 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.
system_import_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the system_import_account 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 system_import_account. 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.
system_import_account 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.