Get statistics about a repository including triple counts,
AI agents call get_statistics 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 retrieves statistical metadata about an RDF repository (triple counts and related metrics). It performs a read-only operation with no side effects, matching the 'Read' category definition of retrieving or querying data. The low severity reflects minimal blast radius—misuse would only expose repository metrics, not modify or delete data.
From the tool's definition Tool name 'get_statistics' and description 'Get statistics about a repository including triple counts' indicate retrieval of aggregate data without modification. No mutations, deletions, or external operations mentioned.
Attacks that exploit this kind of access
Get statistics about a repository including triple counts,. 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_statistics: 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_statistics 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_statistics 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_statistics. 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_statistics 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 →