get_beacon_signing_key
Get details of a specific beacon signing key by ID
This record as markdown: /tools/adbutler/get-beacon-signing-key.md
What get_beacon_signing_key does on AdButler
AI agents call get_beacon_signing_key to retrieve information from AdButler 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 | number | Yes | Beacon signing key ID |
Parameters from the server's own tool schema.
Why get_beacon_signing_key is rated Low
This tool retrieves signing key details from the AdButler system without creating, modifying, or deleting any data. It is a straightforward read operation. While signing keys are sensitive cryptographic material, the tool only retrieves existing details without enabling deployment or modification of keys, keeping severity low.
From the tool's definition Tool name contains 'get' and description states 'Get details of a specific beacon signing key by ID'. These are retrieval operations with no modification.
Attacks that exploit this kind of access
The rule that runs get_beacon_signing_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_beacon_signing_key, this is the rule to start with:
get_beacon_signing_key is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every get_beacon_signing_key call is checked against it from then on.
Questions about get_beacon_signing_key
Get details of a specific beacon signing key by ID. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
get_beacon_signing_key accepts 1 parameter: id. Required: id. 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 get_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.
get_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 get_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 get_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.
get_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.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue