AI agents call list_public_holiday_calendars to retrieve information from Humaans without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns a list of public holiday calendar configurations. It performs no modifications, deletions, or external operations. The server itself is documented as read-only, and this tool fits the Read category pattern (list = retrieve data). Severity is low because leaked public holiday information poses minimal risk to an organization.
From the tool's definition Server is explicitly 'Read-only MCP server' and tool 'list_public_holiday_calendars' retrieves/queries configured calendars with no side effects. The verb 'list' and the function context confirm data retrieval only.
Attacks that exploit this kind of access
List all configured public holiday calendars. It is categorised as a Read tool in the Humaans MCP Server, which means it retrieves data without modifying state.
Register the Humaans MCP server in PolicyLayer and add a rule for list_public_holiday_calendars: 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 Humaans. Nothing to install.
list_public_holiday_calendars 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_public_holiday_calendars 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_public_holiday_calendars. 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_public_holiday_calendars is provided by the Humaans MCP server (ptorsten/humaans-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 →