teams_get_team

Get details of a specific team

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/teams-get-team.md

WHAT IT DOES

What teams_get_team does on Sage MCP

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

RISK

Why teams_get_team is rated Low

This tool retrieves team metadata/details without creating, modifying, deleting, executing commands, or triggering financial transactions. It is a straightforward read operation. Severity is low because exposing team details has minimal blast radius compared to write, execute, or destructive operations—it primarily reveals information that may already be accessible through normal organizational channels.

From the tool's definition Tool name 'teams_get_team' with description 'Get details of a specific team' indicates a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs teams_get_team safely

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

teams_get_team Allowed

teams_get_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": {
    "teams_get_team": {}
  }
}

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

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

FAQ

Questions about teams_get_team

What does the teams_get_team tool do? +

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

How do I enforce a policy on teams_get_team? +

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

What risk level is teams_get_team? +

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

Can I rate-limit teams_get_team? +

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

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

teams_get_team is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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