floating_release · LicenseSpring MCP Server MCP

WHAT IT DOES

What floating_release does on LicenseSpring MCP Server

AI agents use floating_release 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.

WHY IT NEEDS A POLICY

Why floating_release needs a policy

An AI agent can call floating_release 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

Recommended rule Ready

Verdict

floating_release Rate-limited

floating_release 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "floating_release": {
      "limits": [
        {
          "counter": "floating_release_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LicenseSpring MCP Server, so you can run agents against it safely.

FAQ

Questions about floating_release

What does the floating_release tool do? +

Release a floating 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.

How do I enforce a policy on floating_release? +

Register the LicenseSpring MCP Server MCP server in PolicyLayer and add a rule for floating_release: 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.

What risk level is floating_release? +

floating_release is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit floating_release? +

Yes. Add a rate_limit block to the floating_release 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.

How do I block floating_release completely? +

Set action: deny in the PolicyLayer policy for floating_release. 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.

What MCP server provides floating_release? +

floating_release 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.