liara_get_release

THE RISK

Low Risk

Why liara_get_release needs a policy

This tool retrieves or queries information about a release without creating, modifying, or deleting any data. It is a read-only operation that returns details, consistent with the Read category which encompasses search, list, get, and fetch operations.

From the tool's definition Tool name 'liara_get_release' and description 'Get details of a specific release' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access liara_get_release gives an agent:

POLICY

How to control liara_get_release

PolicyLayer is an MCP gateway — it sits between your AI agents and Liara MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for liara_get_release:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "liara_get_release": {}
  }
}

liara_get_release is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Liara MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Liara MCP Server tools

Destructive liara_delete_app Delete an app Destructive liara_delete_backup Delete a database backup Destructive liara_delete_bucket Delete a storage bucket Destructive liara_delete_database Delete a database Destructive liara_delete_disk Delete a disk Destructive liara_delete_dns_record Delete a DNS record Destructive liara_delete_env_var Delete/unset an environment variable for an app Destructive liara_delete_env_vars Delete/unset multiple environment variables for an app

All 108 Liara MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about liara_get_release

What does the liara_get_release tool do? +

Get details of a specific release. It is categorised as a Read tool in the Liara MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on liara_get_release? +

Register the Liara MCP Server MCP server in PolicyLayer and add a rule for liara_get_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 Liara MCP Server. Nothing to install.

What risk level is liara_get_release? +

liara_get_release is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit liara_get_release? +

Yes. Add a rate_limit block to the liara_get_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 liara_get_release completely? +

Set action: deny in the PolicyLayer policy for liara_get_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 liara_get_release? +

liara_get_release is provided by the Liara MCP Server MCP server (razavioo/liara-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Liara MCP Server tool call.

Start from Liara MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →