memory_wiki_refresh

Refresh wiki articles that have stale content (memories updated since last compile). Only recompiles affected articles instead of regenerating everything.

Server Exocortex shawnhack/exocortex
Category Read
Risk class Low
Parameters 00 required

What memory_wiki_refresh does on Exocortex

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

Why memory_wiki_refresh needs a policy

Even though memory_wiki_refresh only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

Questions about memory_wiki_refresh

What does the memory_wiki_refresh tool do? +

Refresh wiki articles that have stale content (memories updated since last compile). Only recompiles affected articles instead of regenerating everything. It is categorised as a Read tool in the Exocortex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_wiki_refresh? +

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

What risk level is memory_wiki_refresh? +

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

Can I rate-limit memory_wiki_refresh? +

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

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

memory_wiki_refresh is provided by the Exocortex MCP server (shawnhack/exocortex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.