AI agents call get_events_tool to retrieve information from Apps Script MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and absence of action words like create, delete, or modify indicate a read operation. The 'get_' prefix is a standard convention for data retrieval with no side effects. While the empty description lowers confidence, the name itself is sufficiently clear. Classification as Read reflects minimal risk—the tool queries/retrieves data without altering state or triggering external operations.
From the tool's definition Tool name 'get_events_tool' indicates retrieval of event data. No description provided, but naming convention and context within a Google Apps Script server that includes event creation (create_event_tool) suggests this retrieves calendar or event information…
Documented attack patterns abuse exactly the kind of access get_events_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apps Script MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_events_tool:
{
"version": "1",
"default": "deny",
"tools": {
"get_events_tool": {}
}
}get_events_tool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_events_tool. It is categorised as a Read tool in the Apps Script MCP MCP Server, which means it retrieves data without modifying state.
Register the Apps Script MCP server in PolicyLayer and add a rule for get_events_tool: 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 Apps Script MCP. Nothing to install.
get_events_tool 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 get_events_tool 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 get_events_tool. 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.
get_events_tool is provided by the Apps Script MCP server (sam-ent/google-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apps Script MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
60 Apps Script MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.