Gets detailed schema information for a specific table
AI agents call read-resource to retrieve information from Nile without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves schema metadata about a database table. This is a read-only operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only learn table structure, which does not compromise data integrity or trigger destructive actions.
From the tool's definition Tool description states 'Gets detailed schema information for a specific table' — a purely informational retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access read-resource gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nile, and nothing reaches the server without passing your rules. This is the rule we recommend for read-resource:
{
"version": "1",
"default": "deny",
"tools": {
"read-resource": {}
}
}read-resource is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Gets detailed schema information for a specific table. It is categorised as a Read tool in the Nile MCP Server, which means it retrieves data without modifying state.
Register the Nile MCP server in PolicyLayer and add a rule for read-resource: 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 Nile. Nothing to install.
read-resource 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 read-resource 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 read-resource. 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.
read-resource is provided by the Nile MCP server (@niledatabase/nile-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nile, 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.
11 Nile tools catalogued and risk-classified — across an index of 43,000+ MCP servers.