Use this tool when you need to set a participant\
AI agents use setParticipantPreferences to create or update resources in Mcp Meetsync — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Meetsync environment.
This tool falls under Write because it modifies participant data (preferences) reversibly. It does not retrieve data (Read), execute arbitrary code (Execute), delete irreversibly (Destructive), or move money (Financial).
From the tool's definition setParticipantPreferences — tool modifies participant configuration/preferences data. The description is incomplete (cuts off mid-sentence: 'set a participant\'), but the name and context indicate it creates or updates participant preference records, which is…
Attacks that exploit this kind of access
Use this tool when you need to set a participant\. It is categorised as a Write tool in the Mcp Meetsync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Meetsync MCP server in PolicyLayer and add a rule for setParticipantPreferences: 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.
setParticipantPreferences is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setParticipantPreferences 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 setParticipantPreferences. 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.
setParticipantPreferences 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 →