Check current credentials status
AI agents call get_credentials_status to retrieve information from Yandex Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of credentials without modifying, executing, or destroying any resources. It is a passive information retrieval operation consistent with the Read category. The low severity reflects minimal blast radius—credential status disclosure is informational but not actionable for unauthorized changes.
From the tool's definition Tool name 'get_credentials_status' and description 'Check current credentials status' indicate a retrieval operation. The server is explicitly described as 'Read-only MCP server' with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Check current credentials status. It is categorised as a Read tool in the Yandex Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yandex Cloud MCP Server MCP server in PolicyLayer and add a rule for get_credentials_status: 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 Yandex Cloud MCP Server. Nothing to install.
get_credentials_status 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_credentials_status 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_credentials_status. 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_credentials_status is provided by the Yandex Cloud MCP Server MCP server (romati88/ycmcp). 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 →