Low Risk

graeae.modes

List GRAEAE consultation modes + their descriptions.

How to control graeae.modes ↓

What graeae.modes does on Mnemos

AI agents call graeae.modes 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 graeae.modes needs a policy

This is a straightforward list/query operation that retrieves metadata about available consultation modes. It has no side effects, does not modify data, execute code, delete anything, or move money. The read-only nature and informational purpose classify it as Read severity low.

From the tool's definition Tool name 'graeae.modes' and description 'List GRAEAE consultation modes + their descriptions' indicate a retrieval operation that queries and returns configuration or mode information.

Documented attack patterns abuse exactly the kind of access graeae.modes gives an agent:

How to control graeae.modes

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 graeae.modes:

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

graeae.modes 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 graeae.modes

What does the graeae.modes tool do? +

List GRAEAE consultation modes + their descriptions. 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 graeae.modes? +

Register the Mnemos MCP server in PolicyLayer and add a rule for graeae.modes: 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 graeae.modes? +

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

Can I rate-limit graeae.modes? +

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

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

graeae.modes 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.