Skip to main content
Glama

mcp_scan_uploads

Scans the WordPress uploads directory to detect executable files and suspicious double extensions, returning read-only findings with paths, hashes, and benign-file reasons.

Instructions

Scan the uploads directory for executable files (.php, .phtml, .phar, .pht, .phps, .shtml, .cgi, also double extensions like x.php.jpg). Read-only; symlinks are not followed. Each finding has path, size, modified, sha256, benign and reason (a code-free 'Silence is golden' index.php, or a known plugin file such as a Borlabs Cookie compatibility patch, checked by active plugin + path + the file's own guard; cvrt-mcp-endpoints 1.16.1+). Caps: 500 findings, 200000 files (truncated says so). cvrt-mcp-endpoints 1.16.0+.

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": {
      "site": "<site>"
    },
    "name": "mcp_scan_uploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does it well: it declares read-only operation, that symlinks are not followed, the exact per-finding fields, the semantics of 'benign'/'reason' including the allowlist logic (active plugin + path + file's own guard), and hard caps of 500 findings / 200000 files with an explicit truncation signal. The minimum-version notes (1.16.0+, 1.16.1+ for the allowlist) are extra operational context an agent would otherwise have to discover by failure.

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

Conciseness4/5

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

Front-loaded with purpose, then behavior, then return shape, then limits, then version gating — a sensible funnel. It is dense with parentheticals (allowlist logic, version tags, extension lists) that are informative rather than wasteful, though the extension enumeration is longer than strictly needed.

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

Completeness5/5

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

For a one-parameter, no-output-schema, no-annotation tool, the description substitutes for the missing output documentation by naming every finding field and explaining the benign/reason classification, and it discloses scale limits. Nothing an agent needs in order to call this correctly or interpret results is missing.

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

Parameters3/5

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

The schema has a single required 'site' parameter with 100% description coverage, so the schema already explains it ('Site id (see list_sites)'). The description adds nothing about the parameter, so the baseline of 3 applies.

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?

States a specific verb and target ('Scan the uploads directory for executable files') and then enumerates the extensions and double-extension pattern it treats as executable, so the agent knows exactly what the tool matches. It is unambiguous against sibling tools, none of which scan the filesystem for executable artifacts.

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?

Usage is only implied: a security/malware audit of uploads is the obvious trigger, but the description never says when to prefer this over something like media_scan_urls or what preconditions exist (e.g. plugin version gating, site access). No alternatives or exclusions are named.

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

Deploy Server

Other Tools