Добавляет репозиторий для индексации и индексирует его.
AI agents use add_repo to create or update resources in Booster MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Booster MCP environment.
This tool creates a new indexed entry for a repository, which is a reversible write operation. It does not execute code, delete data, or move money. The severity is medium because misconfiguration could cause the system to index unintended repositories or consume computational resources, but the operation is reversible.
From the tool's definition Tool name 'add_repo' and description 'Добавляет репозиторий для индексации и индексирует его' (Adds a repository for indexing and indexes it) indicates the tool creates or modifies indexed data in the system.
Attacks that exploit this kind of access
Добавляет репозиторий для индексации и индексирует его. It is categorised as a Write tool in the Booster MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Booster MCP server in PolicyLayer and add a rule for add_repo: 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 Booster MCP. Nothing to install.
add_repo 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 add_repo 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 add_repo. 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.
add_repo is provided by the Booster MCP server (neuroghostdev/booster_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 →