operant-mcp

Official

Overview Schema Source Related Servers Discussions Admin

ssrf_cloud_metadata

Test SSRF vulnerabilities by accessing cloud metadata endpoints (AWS/GCP/Azure) to identify potential exposure of IAM credentials and instance data.

Instructions

Test SSRF access to cloud metadata endpoints (AWS/GCP/Azure). Attempts to reach instance metadata services through the SSRF vector. Returns results array with provider, endpoint, status, length, response_snippet. Side effects: May cause target to request cloud metadata. Could expose IAM credentials if successful.

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": {
      "url": "<url>",
      "parameter": "<parameter>"
    },
    "name": "ssrf_cloud_metadata"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Target URL with SSRF-vulnerable parameter
`parameter`	Yes	Parameter that accepts URLs
`cloud_provider`	No	Cloud provider to test metadata endpoints for
`method`	No	HTTP method

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description carries full burden and does so effectively. It clearly discloses the tool's behavior: it attempts to reach metadata services through SSRF, returns specific result fields, and importantly warns about side effects (may cause target to request cloud metadata, could expose IAM credentials if successful). This provides crucial behavioral context beyond what parameters indicate.

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 perfectly sized and front-loaded: first sentence states the purpose, second describes the return format, third warns about side effects. Every sentence earns its place with zero wasted words.

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 security testing tool with no annotations and no output schema, the description provides excellent context about behavior and side effects. However, it doesn't describe the format or structure of the returned results array in detail, leaving some ambiguity about what 'status', 'length', and 'response_snippet' actually contain.

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?

With 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description doesn't add additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the specific action ('Test SSRF access to cloud metadata endpoints'), identifies the target resources (AWS/GCP/Azure metadata services), and distinguishes it from the sibling 'ssrf_test' tool by focusing specifically on cloud metadata exploitation rather than general SSRF testing.

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?

The description implies usage context (testing SSRF vulnerabilities targeting cloud metadata) but doesn't explicitly state when to use this tool versus the general 'ssrf_test' sibling or other security testing tools. It provides good context but lacks explicit alternative guidance.

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

Deploy Server