AI agents call list_calendar_runs to retrieve information from PeopleSoft MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name prefix 'list_' combined with the pattern of other read-only tools on this server strongly indicates a data retrieval operation with no side effects. Empty description lowers confidence slightly, but the naming convention is clear enough to classify as Read with low severity, as it only queries existing data.
From the tool's definition Tool name 'list_calendar_runs' indicates a retrieval operation. The description is empty, but the name structure and context among sibling tools (get_accumulator_balances, get_beneficiaries, get_employee, etc.) suggests this retrieves or lists calendar run…
Documented attack patterns abuse exactly the kind of access list_calendar_runs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PeopleSoft MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_calendar_runs:
{
"version": "1",
"default": "deny",
"tools": {
"list_calendar_runs": {}
}
}list_calendar_runs 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.
list_calendar_runs. It is categorised as a Read tool in the PeopleSoft MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PeopleSoft MCP Server MCP server in PolicyLayer and add a rule for list_calendar_runs: 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 PeopleSoft MCP Server. Nothing to install.
list_calendar_runs 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 list_calendar_runs 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 list_calendar_runs. 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.
list_calendar_runs is provided by the PeopleSoft MCP Server MCP server (rgrz/peoplesoft-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PeopleSoft MCP Server, 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.
23 PeopleSoft MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.