get_working_memory

Retrieve working memory for a session, or the most recent entries if no session given.

SERVERMetis Public Health SOURCEsveritg/metis_ph

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sveritg-metis-ph/get-working-memory.md

WHAT IT DOES

What get_working_memory does on Metis Public Health

AI agents call get_working_memory to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_working_memory is rated Low

This tool fetches existing session data or recent memory entries without creating, modifying, deleting, or executing operations. The read-only nature ('retrieve') and absence of any mutative language places it squarely in the Read category.

From the tool's definition "Retrieve working memory for a session, or the most recent entries if no session given" — the verb 'retrieve' indicates data querying with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_working_memory safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_working_memory, this is the rule to start with:

get_working_memory Allowed

get_working_memory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_working_memory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every get_working_memory call is checked against it from then on.

FAQ

Questions about get_working_memory

What does the get_working_memory tool do? +

Retrieve working memory for a session, or the most recent entries if no session given. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_working_memory? +

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

What risk level is get_working_memory? +

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

Can I rate-limit get_working_memory? +

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

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

get_working_memory is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →