Low Risk

graeae.muses

List available GRAEAE muses (LLM providers + models).

How to control graeae.muses ↓

What graeae.muses does on Mnemos

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

This is a straightforward listing/querying operation with no side effects. It retrieves information about available LLM providers and models for informational purposes only. The action 'List' is explicitly read-only, and there is no capability to modify, delete, execute external operations, or commit financial transactions.

From the tool's definition Tool name 'graeae.muses' with description 'List available GRAEAE muses (LLM providers + models)' indicates a read-only query operation that retrieves configuration or metadata about available LLM providers and models.

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

How to control graeae.muses

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.muses:

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

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

What does the graeae.muses tool do? +

List available GRAEAE muses (LLM providers + models). 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.muses? +

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

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

Can I rate-limit graeae.muses? +

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

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

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