AgentsID Guard

Official

Overview Schema Source Related Servers Discussions Admin

shell_run

Run shell commands with enforcement of permission rules: read operations allowed, destructive commands blocked unless permitted.

Instructions

Run a shell command. Validated against AgentsID permissions. Read commands (ls, cat, grep) typically allowed. Destructive commands (rm, chmod) blocked unless permitted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "shell_run"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	The shell command to run

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the permission validation ('Validated against AgentsID permissions') and typical allow/block behavior for read vs destructive commands. This provides significant operational context, though it omits details about output handling and error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loaded with the core action. The second sentence efficiently adds crucial permission context without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no annotations and no output schema, the description covers the essential purpose and permission constraints. It lacks details on output format and failure modes, but the simplicity of the tool makes this a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes 'command' as 'The shell command to run' (100% coverage). The description adds value by illustrating concrete command examples (ls, cat, grep; rm, chmod) and associating them with permission outcomes, which aids in constructing valid inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Run a shell command' with a clear verb and resource. It distinguishes itself from wrapper tools like git_run or ssh_run by covering arbitrary shell commands, even though it doesn't name alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives guidance on command types: 'Read commands (ls, cat, grep) typically allowed' and 'Destructive commands (rm, chmod) blocked unless permitted.' This helps the agent know what to run, but it does not explicitly address when to use this tool versus sibling tools like file_read or ssh_run.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.