AI agents call get_date to retrieve information from Iris MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple query operation that returns read-only system information. No data is created, modified, deleted, or executed. The potential blast radius is minimal since date/time information is non-sensitive and read-only access cannot cause harm.
From the tool's definition Tool retrieves the current system date and time with no modification or side effects. Description explicitly states 'Get' operation.
Attacks that exploit this kind of access
Get the current system date and time. It is categorised as a Read tool in the Iris MCP MCP Server, which means it retrieves data without modifying state.
Register the Iris MCP server in PolicyLayer and add a rule for get_date: 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 Iris MCP. Nothing to install.
get_date 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_date 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_date. 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_date is provided by the Iris MCP server (jenova-marie/iris-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 →