This record as markdown: /tools/ashlesh-t-cognirepo/link-repos.md
What link_repos does on CogniRepo
AI agents use link_repos to create or update resources in CogniRepo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CogniRepo environment.
Why link_repos is rated Medium
With no description available, classification is based solely on the tool name. 'link_repos' strongly implies creating or establishing a connection/association between repositories, which is a Write operation (creating a new relationship). Confidence is low due to the empty description — it could also be Execute if it triggers processes, but Write is the most likely interpretation.
From the tool's definition Tool name 'link_repos' and empty description. The name suggests creating a relationship or association between repositories.
Attacks that exploit this kind of access
The rule that runs link_repos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CogniRepo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For link_repos, this is the rule to start with:
link_repos stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CogniRepo, apply this rule, and every link_repos call is checked against it from then on.
Questions about link_repos
link_repos is a write tool on the CogniRepo MCP server. It is categorised as a Write tool in the CogniRepo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CogniRepo MCP server in PolicyLayer and add a rule for link_repos: 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 CogniRepo. Nothing to install.
link_repos 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 link_repos 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 link_repos. 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.
link_repos is provided by the CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CogniRepo, and thousands of servers like it.
This server
Across the catalogue