get_schema_summary

Get an overview of the ontology schema including statistics,

Server RDF4J MCP Server odysa/rdf4j-mcp
Category Read
Risk class Low
Parameters 00 required

What get_schema_summary does on RDF4J MCP Server

AI agents call get_schema_summary 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.

Why get_schema_summary needs a policy

This tool retrieves ontology schema information and statistics from an RDF repository. It is a read-only operation with no side effects on data or system state. The evidence from both the name and description clearly indicates data retrieval/query functionality, placing it in the Read category. Severity is low because retrieval of schema information poses minimal risk even if accessed by an untrusted AI agent.

From the tool's definition Tool name 'get_schema_summary' and description 'Get an overview of the ontology schema including statistics' indicate a retrieval operation that queries and returns schema metadata without modifying, executing code, or performing destructive operations.

Questions about get_schema_summary

What does the get_schema_summary tool do? +

Get an overview of the ontology schema including statistics,. It is categorised as a Read tool in the RDF4J MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_schema_summary? +

Register the RDF4J MCP Server MCP server in PolicyLayer and add a rule for get_schema_summary: 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.

What risk level is get_schema_summary? +

get_schema_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_schema_summary? +

Yes. Add a rate_limit block to the get_schema_summary 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.

How do I block get_schema_summary completely? +

Set action: deny in the PolicyLayer policy for get_schema_summary. 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.

What MCP server provides get_schema_summary? +

get_schema_summary 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.