Create a new Posterly API key for the authenticated user. SECRET-CREATING WRITE: only use after explicit user confirmation. The new key can only request scopes already present on the calling dashboard-created API key; OAuth and managed assistant tokens cannot mint keys.
AI agents use create_api_key to create or update resources in Posterly — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Posterly environment.
This tool creates a new API key credential, which is a write operation that creates a reversible but sensitive asset. While the tool itself includes a safeguard requiring explicit user confirmation and restricts scopes, the creation of API keys is a Write action (not Execute, as it doesn't run code; not Financial, as it doesn't move money; not Destructive, as keys can be revoked).
From the tool's definition Tool description explicitly states 'SECRET-CREATING WRITE' and 'Create a new Posterly API key for the authenticated user.' Creates a new API key credential that persists and grants API access.
Attacks that exploit this kind of access
Create a new Posterly API key for the authenticated user. SECRET-CREATING WRITE: only use after explicit user confirmation. The new key can only request scopes already present on the calling dashboard-created API key; OAuth and managed assistant tokens cannot mint keys. It is categorised as a Write tool in the Posterly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Posterly MCP server in PolicyLayer and add a rule for create_api_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 Posterly. Nothing to install.
create_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_api_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 create_api_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.
create_api_key is provided by the Posterly MCP server (posterly-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 →