clickru_api_call
AI agents invoke clickru_api_call to trigger actions in SergeyKrin9/mcp Servers. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The description is empty and uninformative, which lowers confidence. However, the name 'clickru_api_call' strongly implies executing arbitrary API calls against the Click.ru platform. Given the server context — which handles advertising campaigns, financial ad spend, and creative publishing — an arbitrary API call could span Read, Write, Execute, Financial, or Destructive actions depending on arguments.
From the tool's definition Tool name 'clickru_api_call' and server context (Click.ru unified ad platform covering Telegram Ads, VK Ads, Yandex.Direct)
Attacks that exploit this kind of access
clickru_api_call. It is categorised as a Execute tool in the SergeyKrin9/mcp Servers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SergeyKrin9/mcp Servers MCP server in PolicyLayer and add a rule for clickru_api_call: 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.
clickru_api_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clickru_api_call 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 clickru_api_call. 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.
clickru_api_call 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 →