get-table-info

THE RISK

Low Risk

Why get-table-info needs a policy

This tool retrieves schema and structural information about database tables—a read-only operation with no side effects, data modification, code execution, or destructive capability. The blast radius of misuse is minimal, limited to information disclosure about table structure.

From the tool's definition Tool name 'get-table-info' and description 'Belirli bir tablo hakkında detaylı bilgi al' (Turkish: 'Get detailed information about a specific table') indicates retrieval of metadata without modification or execution of arbitrary operations.

Documented attack patterns abuse exactly the kind of access get-table-info gives an agent:

POLICY

How to control get-table-info

PolicyLayer is an MCP gateway — it sits between your AI agents and PostGIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-table-info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-table-info": {}
  }
}

get-table-info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register PostGIS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-table-info

What does the get-table-info tool do? +

Belirli bir tablo hakkında detaylı bilgi al. It is categorised as a Read tool in the PostGIS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-table-info? +

Register the PostGIS MCP Server MCP server in PolicyLayer and add a rule for get-table-info: 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 PostGIS MCP Server. Nothing to install.

What risk level is get-table-info? +

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

Can I rate-limit get-table-info? +

Yes. Add a rate_limit block to the get-table-info 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-table-info completely? +

Set action: deny in the PolicyLayer policy for get-table-info. 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-table-info? +

get-table-info is provided by the PostGIS MCP Server MCP server (receptopalak/postgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PostGIS MCP Server tool call.

Start from PostGIS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →