graeae.get

THE RISK

Low Risk

Why graeae.get needs a policy

The 'get' operation retrieves stored consultation data by identifier. This is a read-only query with no ability to modify, delete, or execute code. No financial or destructive operations are possible.

From the tool's definition Tool description states 'Get a previous GRAEAE consultation by id' — a retrieval operation with no modification or side effects.

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

POLICY

How to control graeae.get

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "graeae.get": {}
  }
}

graeae.get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Mnemos — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mnemos tools

Execute graeae.consult Submit a multi-LLM consensus consultation to GRAEAE (PYTHIA). Modes: auto/single/all/debat Execute hive.message_publish Publish a Hive message. to_urn=null for broadcast. Write hive.job_next Atomic dequeue: claim highest-priority eligible job for this agent. Returns job or {204: n Write hive.agent_register Register this session as an agent in the Hive. Returns urn + session_id. Write hive.job_create Submit work into the Hive Mind triage queue. Eligible agents self-claim. Write hive.job_update Update job status/result. Status: queued/claimed/running/done/failed/cancelled. Write mnemos.memory_create Save a memory to MNEMOS. Category: infrastructure/solutions/patterns/decisions/projects/st Read graeae.modes List GRAEAE consultation modes + their descriptions.

All 15 Mnemos tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about graeae.get

What does the graeae.get tool do? +

Get a previous GRAEAE consultation by id. 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.get? +

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

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

Can I rate-limit graeae.get? +

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

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

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

CHECK YOUR STACK →