AI agents use update_subscription to create or update resources in Creem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Creem environment.
This tool creates or modifies subscription data reversibly—specifically changing subscription parameters like seat counts or units. While it affects financially-relevant entities, it does not itself move money or create new financial obligations (that would be create_checkout or similar); it modifies existing subscriptions.
From the tool's definition Tool description states 'Update subscription (e.g., change number of seats/units)' which modifies existing subscription data.
Attacks that exploit this kind of access
Update subscription (e.g., change number of seats/units). It is categorised as a Write tool in the Creem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Creem MCP server in PolicyLayer and add a rule for update_subscription: 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 Creem. Nothing to install.
update_subscription 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 update_subscription 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 update_subscription. 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.
update_subscription is provided by the Creem MCP server (selenium39/mcp-server-creem). 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 →