AI agents call validate_beacon_signing_key to retrieve information from AdButler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | — | Beacon signing key to validate |
Parameters from the server's own tool schema.
Validation operations are read-only checks that retrieve or verify information about existing data (in this case, a signing key's validity). No data is created, modified, deleted, or used to trigger external operations. The tool performs authentication/verification logic, which is a non-destructive inspection of state.
From the tool's definition Tool name 'validate_beacon_signing_key' and description 'Validate a beacon signing key' indicate a validation/verification operation that checks cryptographic key properties without modifying, deleting, or executing external code.
Attacks that exploit this kind of access
Validate a beacon signing key. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
validate_beacon_signing_key accepts 1 parameter: key. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for validate_beacon_signing_key: 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 AdButler. Nothing to install.
validate_beacon_signing_key is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_beacon_signing_key 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.
Set action: deny in the PolicyLayer policy for validate_beacon_signing_key. 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.
validate_beacon_signing_key is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →