Set activation limits for users on a specific license
AI agents use set_user_activations to create or update resources in LicenseSpring MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LicenseSpring MCP Server environment.
An AI agent can call set_user_activations faster than any human can review — one bad instruction and it creates or modifies resources in LicenseSpring MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Set activation limits for users on a specific license. It is categorised as a Write tool in the LicenseSpring MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LicenseSpring MCP Server MCP server in PolicyLayer and add a rule for set_user_activations: 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 LicenseSpring MCP Server. Nothing to install.
set_user_activations 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 set_user_activations 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 set_user_activations. 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.
set_user_activations is provided by the LicenseSpring MCP Server MCP server (stier1ba/licensespring-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.