test_webhook

Queue a signed webhook.test delivery to validate a subscription endpoint.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/test-webhook.md

WHAT IT DOES

What test_webhook does on Starfield

AI agents call test_webhook to retrieve information from Starfield without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`id`	string	Yes	Webhook subscription ID

Parameters from the server's own tool schema.

RISK

Why test_webhook is rated Low

Even though test_webhook only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_webhook safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_webhook, this is the rule to start with:

test_webhook Allowed

test_webhook is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_webhook": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every test_webhook call is checked against it from then on.

FAQ

Questions about test_webhook

What does the test_webhook tool do? +

Queue a signed webhook.test delivery to validate a subscription endpoint. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does test_webhook accept? +

test_webhook accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on test_webhook? +

Register the Starfield MCP server in PolicyLayer and add a rule for test_webhook: 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 Starfield. Nothing to install.

What risk level is test_webhook? +

test_webhook is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test_webhook? +

Yes. Add a rate_limit block to the test_webhook 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.

How do I block test_webhook completely? +

Set action: deny in the PolicyLayer policy for test_webhook. 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.

What MCP server provides test_webhook? +

test_webhook is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →