Get connection details. Optionally include database schema.
AI agents call df_get_connection to retrieve information from DataForge Semantic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it retrieves existing data without creating, modifying, or deleting anything. However, the severity is elevated from 'low' to 'medium' because connection details are high-value targets for lateral movement, credential theft, or unauthorized database access. An AI agent with access to this tool could expose credentials or connection strings to downstream systems or logs.
From the tool's definition Tool name 'df_get_connection' and description 'Get connection details' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Get connection details. Optionally include database schema. It is categorised as a Read tool in the DataForge Semantic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataForge Semantic MCP Server MCP server in PolicyLayer and add a rule for df_get_connection: 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 DataForge Semantic MCP Server. Nothing to install.
df_get_connection 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 df_get_connection 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 df_get_connection. 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.
df_get_connection is provided by the DataForge Semantic MCP Server MCP server (sgromych/dataforge-mcp-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
df_get_connection is one line of DataForge Semantic MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →