Use this tool when you already have the participant\
AI agents call getParticipant to retrieve information from Mcp Meetsync without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing participant data without creating, modifying, or deleting information. It has no side effects and no external impact. The blast radius of misuse is minimal—an agent could only access information about meeting participants, which poses no risk if the participant ID is already known. Classified as Read with low severity.
From the tool's definition Tool name 'getParticipant' and description indicating retrieval of participant information ('when you already have the participant') suggest a query/fetch operation that returns data without modification.
Attacks that exploit this kind of access
Use this tool when you already have the participant\. It is categorised as a Read tool in the Mcp Meetsync MCP Server, which means it retrieves data without modifying state.
Register the Mcp Meetsync MCP server in PolicyLayer and add a rule for getParticipant: 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 Mcp Meetsync. Nothing to install.
getParticipant 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 getParticipant 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 getParticipant. 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.
getParticipant is provided by the Mcp Meetsync MCP server (nicholasemccormick/mcp-meetsync). 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 →