Get status of an ad-hoc command.
AI agents call get_adhoc_command_status to retrieve information from AAP Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves status information about an ad-hoc command that has already been executed. It performs a read-only query with no side effects, no code execution triggered by the tool itself, and no data modification. The minimal blast radius if misused would be information disclosure about command execution status.
From the tool's definition Tool name 'get_adhoc_command_status' and description 'Get status of an ad-hoc command' indicate a retrieval operation that queries the status of an existing command without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get_adhoc_command_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AAP Enterprise MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_adhoc_command_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_adhoc_command_status": {}
}
}get_adhoc_command_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.
Get status of an ad-hoc command. It is categorised as a Read tool in the AAP Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AAP Enterprise MCP Server MCP server in PolicyLayer and add a rule for get_adhoc_command_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 AAP Enterprise MCP Server. Nothing to install.
get_adhoc_command_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 get_adhoc_command_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 get_adhoc_command_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.
get_adhoc_command_status is provided by the AAP Enterprise MCP Server MCP server (sibilleb/aap-enterprise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 69 AAP Enterprise MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
69 AAP Enterprise MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.