gluecron_release_lease
Release a lease by id. Idempotent. Returns {released}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-release-lease.md
What gluecron_release_lease does on Gluecron
AI agents use gluecron_release_lease to create or update resources in Gluecron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gluecron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lease_id | string | Yes |
Parameters from the server's own tool schema.
Why gluecron_release_lease is rated Medium
Releasing a lease is a Write operation—it modifies the state of a resource (the lease) reversibly. The operation is idempotent (safe to retry) and does not delete data or commit financial obligations. It pairs logically with gluecron_acquire_lease (a sibling tool) in a standard acquire/release pattern.
From the tool's definition Tool name 'gluecron_release_lease' and description 'Release a lease by id. Idempotent.' indicates a reversible state modification operation that releases a previously acquired resource.
Attacks that exploit this kind of access
The rule that runs gluecron_release_lease safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_release_lease, this is the rule to start with:
gluecron_release_lease stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_release_lease call is checked against it from then on.
Questions about gluecron_release_lease
Release a lease by id. Idempotent. Returns {released}. It is categorised as a Write tool in the Gluecron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gluecron_release_lease accepts 1 parameter: lease_id. Required: lease_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_release_lease: 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 Gluecron. Nothing to install.
gluecron_release_lease 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 gluecron_release_lease 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 gluecron_release_lease. 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.
gluecron_release_lease is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
This server
Across the catalogue