List all calendars for the authenticated user with stable role enums
AI agents call tweek-mcp to retrieve information from Tweek MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar data for the authenticated user without creating, modifying, deleting, or executing any operations. It is a straightforward query operation with minimal blast radius if misused by an AI agent—at worst, an agent would retrieve calendar information the user is already authorized to access.
From the tool's definition Tool description states 'List all calendars for the authenticated user' — a pure retrieval operation with no modification or side effects. The server description confirms it 'list[s] accessible calendars' as a read-only action.
Attacks that exploit this kind of access
List all calendars for the authenticated user with stable role enums. It is categorised as a Read tool in the Tweek MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tweek MCP Server MCP server in PolicyLayer and add a rule for tweek-mcp: 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 Tweek MCP Server. Nothing to install.
tweek-mcp 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 tweek-mcp 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 tweek-mcp. 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.
tweek-mcp is provided by the Tweek MCP Server MCP server (waspeer/tweek-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 →