Create a Google Meet and send invitation email
AI agents use create_meet_and_send to create or update resources in Gmail Drive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail Drive environment.
An AI agent can call create_meet_and_send faster than any human can review — one bad instruction and it creates or modifies resources in Gmail Drive by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Create a Google Meet and send invitation email. It is categorised as a Write tool in the Gmail Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail Drive MCP server in PolicyLayer and add a rule for create_meet_and_send: 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 Gmail Drive. Nothing to install.
create_meet_and_send 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 create_meet_and_send 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 create_meet_and_send. 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.
create_meet_and_send is provided by the Gmail Drive MCP server (smitpatel-31/gmail-drive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.