Get bid manager settings and status for an account.
AI agents call get_bid_manager to retrieve information from SergeyKrin9/mcp Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration and operational status information from a bid management system (likely Yandex.Direct's bid manager feature). It queries existing data without creating, modifying, deleting, or executing any operations. The blast radius is minimal—misuse would only expose account settings data, not enable unauthorized modifications or financial transactions.
From the tool's definition Tool name 'get_bid_manager' and description 'Get bid manager settings and status for an account' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get bid manager settings and status for an account. It is categorised as a Read tool in the SergeyKrin9/mcp Servers MCP Server, which means it retrieves data without modifying state.
Register the SergeyKrin9/mcp Servers MCP server in PolicyLayer and add a rule for get_bid_manager: 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 SergeyKrin9/mcp Servers. Nothing to install.
get_bid_manager 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_bid_manager 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_bid_manager. 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_bid_manager is provided by the SergeyKrin9/mcp Servers MCP server (sergeykrin9/mcp-servers). 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 →