Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
AI agents use unsubscribe to create or update resources in Thegamesdb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thegamesdb environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Subscription id (uuid) returned by subscribe. |
Parameters from the server's own tool schema.
The tool cancels/deactivates a subscription but explicitly states it is not deleted, preserving historical data. This is a reversible modification (Write), not a Destructive action. However, cancelling a subscription could have downstream consequences (e.g., loss of access), so severity is medium. It is not Financial because no money movement is described — only the subscription record state changes.
From the tool's definition 'Cancel a subscription by id' and 'The row is deactivated (not deleted)' — the subscription record is deactivated reversibly, not permanently deleted
Attacks that exploit this kind of access
Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts. It is categorised as a Write tool in the Thegamesdb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
unsubscribe accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Thegamesdb MCP server in PolicyLayer and add a rule for unsubscribe: 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 Thegamesdb. Nothing to install.
unsubscribe 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 unsubscribe 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 unsubscribe. 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.
unsubscribe is provided by the Thegamesdb MCP server (https://gateway.pipeworx.io/thegamesdb/mcp). 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 →