Use this when ChatGPT should render the service health status as an inline UI card.
AI agents call health.status_card to retrieve information from GPT MCP Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only diagnostic tool that queries and displays the current health status of the service. It has no capacity to modify data, execute commands, delete resources, or trigger external operations. The 'card' rendering is purely presentational. Severity is low because misuse poses minimal risk—an agent could at worst display health information repeatedly, causing negligible impact.
From the tool's definition Tool name 'health.status_card' and description indicate it renders/displays service health status as a UI card.
Attacks that exploit this kind of access
Use this when ChatGPT should render the service health status as an inline UI card. It is categorised as a Read tool in the GPT MCP Service MCP Server, which means it retrieves data without modifying state.
Register the GPT MCP Service MCP server in PolicyLayer and add a rule for health.status_card: 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 GPT MCP Service. Nothing to install.
health.status_card 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 health.status_card 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 health.status_card. 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.
health.status_card is provided by the GPT MCP Service MCP server (jmillpps/encore-mcp-base). 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 →