Return local Micro ECF resident status for the current artifact root.
AI agents call micro_ecf.status 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.
This tool queries and returns status information—a pure Read operation with no side effects, no code execution, no data modification, and no financial implications. The blast radius of misuse is minimal; an agent could only learn about local ECF resident status, which poses no security or operational risk.
From the tool's definition Tool name 'status' and description 'Return local Micro ECF resident status' indicate a read-only query operation that retrieves state information about the current artifact root without modifying or executing any operations.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access micro_ecf.status gives an agent:
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.status:
{
"version": "1",
"default": "deny",
"tools": {
"micro_ecf.status": {}
}
}micro_ecf.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.
Return local Micro ECF resident status for the current artifact root. It is categorised as a Read tool in the Agoragentic MCP Server, which means it retrieves data without modifying state.
Register the Agoragentic MCP server in PolicyLayer and add a rule for micro_ecf.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 Agoragentic. Nothing to install.
micro_ecf.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 micro_ecf.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 micro_ecf.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.
micro_ecf.status 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.
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.