windsurf_get_seat_info

Get team seat allocation info (stub -- API not publicly available,

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/windsurf-get-seat-info.md

WHAT IT DOES

What windsurf_get_seat_info does on Sage MCP

AI agents call windsurf_get_seat_info 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 windsurf_get_seat_info is rated Low

This tool retrieves team seat allocation information, which is a read-only operation that queries data without side effects. The 'Get' verb and the nature of seat info (informational metadata) confirm it as a Read category risk. The 'stub' note and unavailable API status further reduce potential impact.

From the tool's definition Tool name 'windsurf_get_seat_info' and description 'Get team seat allocation info' indicate data retrieval with no modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs windsurf_get_seat_info 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 windsurf_get_seat_info, this is the rule to start with:

windsurf_get_seat_info Allowed

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

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 windsurf_get_seat_info call is checked against it from then on.

FAQ

Questions about windsurf_get_seat_info

What does the windsurf_get_seat_info tool do? +

Get team seat allocation info (stub -- API not publicly available,. 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 windsurf_get_seat_info? +

Register the Sage MCP server in PolicyLayer and add a rule for windsurf_get_seat_info: 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 windsurf_get_seat_info? +

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

Can I rate-limit windsurf_get_seat_info? +

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

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

windsurf_get_seat_info 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 →