[HTTP mode only] Remove all inactive (dead) monitored objects from the Scouter server. Inactive objects are agents that are no longer sending data. Use get_system_overview to check which objects are alive/dead before removing.
AI agents call remove_inactive_objects to permanently remove resources in Scouter — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes monitored objects from the APM server. While the objects are inactive, the removal action cannot be undone and destroys monitoring configuration. This is irreversible data deletion, making it Destructive rather than Write. Severity is high because an agent could accidentally remove all monitoring objects if misused, disrupting APM visibility across the infrastructure.
From the tool's definition Tool description explicitly states "Remove all inactive (dead) monitored objects from the Scouter server" — the verb "Remove" combined with "all" indicates irreversible deletion of data/configuration.
Attacks that exploit this kind of access
[HTTP mode only] Remove all inactive (dead) monitored objects from the Scouter server. Inactive objects are agents that are no longer sending data. Use get_system_overview to check which objects are alive/dead before removing. It is categorised as a Destructive tool in the Scouter MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Scouter MCP server in PolicyLayer and add a rule for remove_inactive_objects: 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 Scouter. Nothing to install.
remove_inactive_objects is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_inactive_objects 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 remove_inactive_objects. 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.
remove_inactive_objects is provided by the Scouter MCP server (scouter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →