Low Risk

neus_agent_link

Readiness check for an agent wallet: returns linked when agent-identity and agent-delegation proofs exist; otherwise link_required with hostedVerifyUrl.

Part of the NEUS MCP server.

neus_agent_link is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NEUS MCP →

Free to start. No card required.

AI agents call neus_agent_link to retrieve information from NEUS MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though neus_agent_link only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full NEUS MCP policy for all 12 tools.

Get this rule live on your own NEUS MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NEUS MCP →

View all 12 tools →

These attack patterns abuse exactly the kind of access neus_agent_link gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so neus_agent_link only ever does what you allow.

SECURE NEUS MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the neus_agent_link tool do? +

Readiness check for an agent wallet: returns linked when agent-identity and agent-delegation proofs exist; otherwise link_required with hostedVerifyUrl.. It is categorised as a Read tool in the NEUS MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on neus_agent_link? +

Register the NEUS MCP server in PolicyLayer and add a rule for neus_agent_link: 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 NEUS MCP. Nothing to install.

What risk level is neus_agent_link? +

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

Can I rate-limit neus_agent_link? +

Yes. Add a rate_limit block to the neus_agent_link 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 neus_agent_link completely? +

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

neus_agent_link is provided by the NEUS MCP server (https://mcp.neus.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NEUS MCP tool call.

Deterministic rules across all 12 NEUS MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.