Low Risk

hive.agent_list

List registered agents in the GRAEAE Hive Mind.

How to control hive.agent_list ↓

What hive.agent_list does on Mnemos

AI agents call hive.agent_list to retrieve information from Mnemos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why hive.agent_list needs a policy

This tool retrieves or enumerates existing data (registered agents) without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query that presents minimal risk even if called by an AI agent, as listing agents does not alter state or trigger external actions.

From the tool's definition Tool name uses 'list' verb and description states 'List registered agents' — a pure query operation with no side effects.

Documented attack patterns abuse exactly the kind of access hive.agent_list gives an agent:

How to control hive.agent_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Mnemos, and nothing reaches the server without passing your rules. This is the rule we recommend for hive.agent_list:

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

hive.agent_list 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 Mnemos — 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 hive.agent_list

What does the hive.agent_list tool do? +

List registered agents in the GRAEAE Hive Mind. It is categorised as a Read tool in the Mnemos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hive.agent_list? +

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

What risk level is hive.agent_list? +

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

Can I rate-limit hive.agent_list? +

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

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

hive.agent_list is provided by the Mnemos MCP server (ncz-os/mnemos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mnemos tool call.

Start from Mnemos, 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.

15 Mnemos 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.