get_current_team

Get the team associated with the current API token.

SERVERCoolify SOURCEcoolify-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/get-current-team.md

WHAT IT DOES

What get_current_team does on Coolify

AI agents call get_current_team to retrieve information from Coolify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_current_team is rated Low

This tool retrieves metadata about the current API token's associated team with no side effects. It queries existing data without modifying, executing code, deleting, or affecting financial systems. The low severity reflects minimal blast radius—an agent retrieving team information poses negligible risk compared to deployment or deletion tools on this server.

From the tool's definition Tool name is 'get_current_team' and description states 'Get the team associated with the current API token.' The verb 'Get' and absence of any modification, creation, deletion, or execution language indicates a read-only retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_current_team safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_current_team, this is the rule to start with:

get_current_team Allowed

get_current_team is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every get_current_team call is checked against it from then on.

FAQ

Questions about get_current_team

What does the get_current_team tool do? +

Get the team associated with the current API token. It is categorised as a Read tool in the Coolify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_team? +

Register the Coolify MCP server in PolicyLayer and add a rule for get_current_team: 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 Coolify. Nothing to install.

What risk level is get_current_team? +

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

Can I rate-limit get_current_team? +

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

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

get_current_team is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →