Low Risk

micro_ecf.work_memory

Read local worklog, docs-sync plan, handoff, and latest summary artifacts. Read-only.

How to control micro_ecf.work_memory ↓

What micro_ecf.work_memory does on Agoragentic

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

Low Risk

Why micro_ecf.work_memory needs a policy

The tool explicitly states it is 'Read-only' and only retrieves local worklog, documentation sync plans, handoffs, and summary artifacts. No data is modified, executed, or deleted. Low severity as it only reads internal work memory artifacts.

From the tool's definition Read local worklog, docs-sync plan, handoff, and latest summary artifacts. Read-only.

Documented attack patterns abuse exactly the kind of access micro_ecf.work_memory gives an agent:

How to control micro_ecf.work_memory

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "micro_ecf.work_memory": {}
  }
}

micro_ecf.work_memory 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 Agoragentic — 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 micro_ecf.work_memory

What does the micro_ecf.work_memory tool do? +

Read local worklog, docs-sync plan, handoff, and latest summary artifacts. Read-only. It is categorised as a Read tool in the Agoragentic MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on micro_ecf.work_memory? +

Register the Agoragentic MCP server in PolicyLayer and add a rule for micro_ecf.work_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 Agoragentic. Nothing to install.

What risk level is micro_ecf.work_memory? +

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

Can I rate-limit micro_ecf.work_memory? +

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

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

micro_ecf.work_memory is provided by the Agoragentic MCP server (rhein1/agoragentic-integrations). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agoragentic tool call.

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

21 Agoragentic 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.