Return when status.redhat.com was last updated.
AI agents call get_last_updated to retrieve information from Red Hat Status MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that returns a timestamp of the last update to a status page. It has no side effects, does not execute commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only waste time querying this information repeatedly.
From the tool's definition Tool name 'get_last_updated' and description 'Return when status.redhat.com was last updated' indicate a simple query operation that retrieves metadata about update timing without modifying data or triggering actions.
Attacks that exploit this kind of access
Return when status.redhat.com was last updated. It is categorised as a Read tool in the Red Hat Status MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Red Hat Status MCP Server MCP server in PolicyLayer and add a rule for get_last_updated: 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 Red Hat Status MCP Server. Nothing to install.
get_last_updated 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_last_updated 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_last_updated. 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_last_updated is provided by the Red Hat Status MCP Server MCP server (jessicarod7/mcp_quickstart_python). 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 →