check_status

Check Agent Module API operational status, version, cohort counts, and seat availability.

SERVERAgent Module SOURCEhttps://api.agent-module.dev/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-agent-module-mcp/check-status.md

WHAT IT DOES

What check_status does on Agent Module

AI agents call check_status to retrieve information from Agent Module without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_status is rated Low

This tool retrieves system and service information without creating, modifying, deleting, or executing any operations. It is a pure information-gathering function with minimal risk; misuse would only expose non-sensitive status data.

From the tool's definition Tool name 'check_status' and description stating it checks 'operational status, version, cohort counts, and seat availability' — all read-only queries with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Module, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_status, this is the rule to start with:

check_status Allowed

check_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agent Module, apply this rule, and every check_status call is checked against it from then on.

FAQ

Questions about check_status

What does the check_status tool do? +

Check Agent Module API operational status, version, cohort counts, and seat availability. It is categorised as a Read tool in the Agent Module MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_status? +

Register the Agent Module MCP server in PolicyLayer and add a rule for check_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 Agent Module. Nothing to install.

What risk level is check_status? +

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

Can I rate-limit check_status? +

Yes. Add a rate_limit block to the check_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.

How do I block check_status completely? +

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

What MCP server provides check_status? +

check_status is provided by the Agent Module MCP server (https://api.agent-module.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Module, and thousands of servers like it.

This server

All 7 Agent Module tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →