List all available RDF repositories.
AI agents call list_repositories 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 retrieves and enumerates available repositories without creating, modifying, deleting, or executing any operations. It is a simple informational query analogous to a list or get operation, with minimal blast radius if misused by an AI agent—it only exposes metadata about available repositories.
From the tool's definition Tool name 'list_repositories' and description 'List all available RDF repositories' indicate a query/retrieval operation with no modification of data.
Attacks that exploit this kind of access
List all available RDF repositories. 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 list_repositories: 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.
list_repositories 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 list_repositories 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 list_repositories. 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.
list_repositories 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 →