Returns the completion state of a previous atelier_hydrate call for the given session_path. Status is
AI agents call atelier_hydrate_status to retrieve information from Mybrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the completion state of a previous operation, making it a pure read operation. It has no destructive, financial, or execute capabilities—it simply retrieves existing status data. The blast radius of misuse is minimal, as an agent cannot cause harm by checking status repeatedly. Low severity assigned because reading status information poses negligible risk.
From the tool's definition Tool name 'atelier_hydrate_status' and description 'Returns the completion state' indicate a query operation that retrieves status information without modification or side effects.
Documented attack patterns abuse exactly the kind of access atelier_hydrate_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mybrain, and nothing reaches the server without passing your rules. This is the rule we recommend for atelier_hydrate_status:
{
"version": "1",
"default": "deny",
"tools": {
"atelier_hydrate_status": {}
}
}atelier_hydrate_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the completion state of a previous atelier_hydrate call for the given session_path. Status is. It is categorised as a Read tool in the Mybrain MCP Server, which means it retrieves data without modifying state.
Register the Mybrain MCP server in PolicyLayer and add a rule for atelier_hydrate_status: 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 Mybrain. Nothing to install.
atelier_hydrate_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the atelier_hydrate_status 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.
Set action: deny in the PolicyLayer policy for atelier_hydrate_status. 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.
atelier_hydrate_status is provided by the Mybrain MCP server (robertsfeir/mybrain). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mybrain, 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.
8 Mybrain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.