Setup Yandex Cloud credentials for the session
AI agents use setup_credentials to create or update resources in Yandex Cloud MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yandex Cloud MCP Server environment.
Setting up credentials is a reversible write operation that modifies session state by establishing authentication. While not immediately destructive, it enables subsequent operations and represents a configuration change. Severity is high because compromised credential setup could lead to unauthorized access or resource misuse, though the action itself is reversible.
From the tool's definition Tool description states 'Setup Yandex Cloud credentials for the session' — this creates or modifies credentials for the current session, which is a write operation that alters state.
Attacks that exploit this kind of access
Setup Yandex Cloud credentials for the session. It is categorised as a Write tool in the Yandex Cloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yandex Cloud MCP Server MCP server in PolicyLayer and add a rule for setup_credentials: 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.
setup_credentials is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setup_credentials 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 setup_credentials. 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.
setup_credentials 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 →