get_seat

A read tool on the Aos MCP server.

SERVERAos SOURCE@funny-booth/aos-mcp-server

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/funny-booth-aos-mcp-server/get-seat.md

WHAT IT DOES

What get_seat does on Aos

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

Parameter	Type	Required	Description
`seat`	string	Yes	座席名
`team_id`	string	—	対象チームID（省略時はユーザーの既定チーム）

Parameters from the server's own tool schema.

RISK

Why get_seat is rated Low

The 'get_' prefix strongly indicates a read operation to retrieve seat information. With no description available, confidence is moderate. No destructive, financial, or code execution indicators are present. Likely queries or fetches seat data with minimal blast radius if misused.

From the tool's definition Tool name 'get_seat' suggests retrieval of seat/resource information. No description provided. Sibling tools include create/complete operations (Write, Execute) but this tool's 'get_' prefix is typical of query operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_seat safely

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

get_seat Allowed

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

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

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

FAQ

Questions about get_seat

What does the get_seat tool do? +

get_seat is a read tool on the Aos MCP server. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.

What parameters does get_seat accept? +

get_seat accepts 2 parameters: seat, team_id. Required: seat. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_seat? +

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

What risk level is get_seat? +

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

Can I rate-limit get_seat? +

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

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

get_seat is provided by the Aos MCP server (@funny-booth/aos-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 Aos, and thousands of servers like it.

This server

All 37 Aos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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