Check connection status for all external services (VITO, Asana, Notion).
AI agents call check_meeting_setup to retrieve information from Meeting Automation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic/status check of external service connections. It retrieves information about whether integrations are connected and operational, but does not create, modify, delete, or execute any operations. It is a safe, informational read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'check_meeting_setup' and description indicate it 'Check[s] connection status for all external services' — a read-only query operation that retrieves status information without modifying any data.
Attacks that exploit this kind of access
Check connection status for all external services (VITO, Asana, Notion). It is categorised as a Read tool in the Meeting Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meeting Automation MCP Server MCP server in PolicyLayer and add a rule for check_meeting_setup: 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 Meeting Automation MCP Server. Nothing to install.
check_meeting_setup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_meeting_setup 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.
Set action: deny in the PolicyLayer policy for check_meeting_setup. 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.
check_meeting_setup is provided by the Meeting Automation MCP Server MCP server (ramhori/meeting-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →