PatchWarden

invoke_discovered_tool

Invoke a discovered tool securely using a token, enforcing checks like command whitelisting and risk assessment for auditable execution.

Instructions

v0.8.1: Invoke a previously discovered tool using a discoveryToken. The token must be obtained from discover_tools first. Enforces 10 security checks: token validity, toolName match, profile allowance, risk ceiling, sensitive path guard, assessment requirement, command whitelist, release confirmation, credential block, and invocation logging. Cannot call itself recursively.

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": {
      "toolName": "<toolName>",
      "arguments": "<arguments>",
      "discoveryToken": "<discoveryToken>"
    },
    "name": "invoke_discovered_tool"
  }
}

Input Schema

Name	Required	Description
`toolName`	Yes	Name of the tool to invoke (must match the discoveryToken's toolName).
`arguments`	Yes	Arguments to pass to the tool. Must match the tool's inputSchema.
`assessmentId`	No	Required for workspace_write/release risk tools. Obtained from the assessment flow.
`discoveryToken`	Yes	Token id from discover_tools. Single-use, expires after 10 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 8, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations provided. Description mentions 10 security checks and that it cannot call itself recursively, adding behavioral context. However, it does not disclose outcomes of checks, error behavior, or side effects beyond the listed constraints.

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?

Single paragraph is front-loaded with version and purpose. Lists 10 security checks concisely without extraneous words. Every sentence adds necessary information.

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

Completeness3/5

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

Covers security checks, token requirement, and recursive call prohibition, but lacks details on return value (no output schema) and error behavior. For a security-sensitive tool, additional context on success/failure outcomes would improve completeness.

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?

Schema coverage is 100% but description adds value: explains token lifecycle (single-use, 10-minute expiration) and condition for assessmentId (required for workspace_write/release risk tools), enhancing understanding beyond schema property descriptions.

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?

Description clearly states it invokes a previously discovered tool using a discoveryToken, with a specific verb 'invoke' and resource 'discovered tool'. It distinguishes from the sibling discover_tools which provides the token.

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

Usage Guidelines4/5

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

Explicitly states prerequisite: 'The token must be obtained from discover_tools first.' Provides clear context for when to use, but does not include explicit when-not-to-use or alternatives beyond the prerequisite.

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

Deploy Server