Execute a SPARQL SELECT query against a temporary ontology store created via HTTP upload. Workflow (HTTP mode only): 1. Call \
AI agents invoke query_uploaded_store to trigger actions in Schema Gov It MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes arbitrary SPARQL SELECT queries against an uploaded ontology store. While SELECT queries are read-only in SPARQL, the tool accepts and runs arbitrary query strings provided by the agent, making it an Execute-category tool.
From the tool's definition "Execute a SPARQL SELECT query against a temporary ontology store created via HTTP upload"
Documented attack patterns abuse exactly the kind of access query_uploaded_store gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Schema Gov It MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_uploaded_store:
{
"version": "1",
"default": "deny",
"tools": {
"query_uploaded_store": {
"limits": [
{
"counter": "query_uploaded_store_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} query_uploaded_store stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a SPARQL SELECT query against a temporary ontology store created via HTTP upload. Workflow (HTTP mode only): 1. Call \. It is categorised as a Execute tool in the Schema Gov It MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Schema Gov It MCP Server MCP server in PolicyLayer and add a rule for query_uploaded_store: 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 Schema Gov It MCP Server. Nothing to install.
query_uploaded_store is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_uploaded_store 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 query_uploaded_store. 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.
query_uploaded_store is provided by the Schema Gov It MCP Server MCP server (italia/dati-semantic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Schema Gov It MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 Schema Gov It MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.