Check credential expiry status (expired, expiring soon, healthy)
AI agents call creds_expiry_check to retrieve information from ML Lab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves expiry information about stored credentials to display status. It performs no modifications, deletions, or execution of external operations. The blast radius of misuse is minimal—an agent could at worst discover which credentials are expired, which is informational only and does not affect system integrity or operations.
From the tool's definition Tool name 'creds_expiry_check' and description 'Check credential expiry status (expired, expiring soon, healthy)' indicate a read-only operation that queries and retrieves credential metadata without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check credential expiry status (expired, expiring soon, healthy). It is categorised as a Read tool in the ML Lab MCP MCP Server, which means it retrieves data without modifying state.
Register the ML Lab MCP server in PolicyLayer and add a rule for creds_expiry_check: 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 ML Lab MCP. Nothing to install.
creds_expiry_check 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 creds_expiry_check 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 creds_expiry_check. 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.
creds_expiry_check is provided by the ML Lab MCP server (pushpullcommitpush/ml-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 →