Get the currently selected default repository ID.
AI agents call get_current_repository to retrieve information from RDF4J MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns the currently active repository identifier. It performs no modifications, deletions, or external operations. It is a simple read operation that retrieves existing configuration state. Severity is low because misuse (e.g., repeatedly calling it) poses no security risk beyond information disclosure of a benign identifier.
From the tool's definition Tool name 'get_current_repository' and description 'Get the currently selected default repository ID' indicate a retrieval operation with no side effects. Returns state information only.
Attacks that exploit this kind of access
Get the currently selected default repository ID. It is categorised as a Read tool in the RDF4J MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RDF4J MCP Server MCP server in PolicyLayer and add a rule for get_current_repository: 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 RDF4J MCP Server. Nothing to install.
get_current_repository 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_current_repository 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_current_repository. 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_current_repository is provided by the RDF4J MCP Server MCP server (odysa/rdf4j-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 →