memory_job_health · Exocortex MCP: Risk & Policy

WHAT IT DOES

What memory_job_health does on Exocortex

AI agents use memory_job_health to create or update resources in Exocortex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Exocortex environment.

WHY IT NEEDS A POLICY

Why memory_job_health needs a policy

The tool writes/logs job execution outcomes when record_outcome is provided, and reads health summaries when omitted. Since it can both write and read, the most severe applicable category is Write. Misuse could corrupt job health records or mask failing jobs, leading to medium severity.

From the tool's definition Record job execution outcomes and query job health. Use record_outcome to log a job run

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_job_health Rate-limited

memory_job_health stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_job_health": {
      "limits": [
        {
          "counter": "memory_job_health_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Exocortex, so you can run agents against it safely.

FAQ

Questions about memory_job_health

What does the memory_job_health tool do? +

Record job execution outcomes and query job health. Use record_outcome to log a job run, or omit it to get a health summary. Jobs below 70% success rate over 3+ runs are flagged as alerts. It is categorised as a Write tool in the Exocortex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_job_health? +

Register the Exocortex MCP server in PolicyLayer and add a rule for memory_job_health: 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_job_health? +

memory_job_health is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_job_health? +

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

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

memory_job_health 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.