view_meeting_requests
AI agents call view_meeting_requests to retrieve information from Schedulia MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries meeting requests without modifying, executing, or deleting data. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an agent could only view requests it has access to, which is a read-only concern. Confidence is high due to the explicit 'view' verb in the name and consistency with the server's declared functionality.
From the tool's definition Tool name 'view_meeting_requests' combined with server description stating it 'enables users to view schedules, manage incoming requests' indicates a read-only retrieval operation.
Attacks that exploit this kind of access
view_meeting_requests. It is categorised as a Read tool in the Schedulia MCP MCP Server, which means it retrieves data without modifying state.
Register the Schedulia MCP server in PolicyLayer and add a rule for view_meeting_requests: 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 Schedulia MCP. Nothing to install.
view_meeting_requests 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 view_meeting_requests 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 view_meeting_requests. 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.
view_meeting_requests is provided by the Schedulia MCP server (watanka/schedulia-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 →