AI agents call get_sql_generation_prompt to retrieve information from JVLink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
No description is provided, which reduces confidence slightly. However, the naming pattern and context (a cohort of non-destructive data schema/documentation tools) strongly indicate this retrieves metadata or templates for SQL generation rather than executing code or modifying state. The worst plausible misuse would be leaking schema or documentation, which is a Read-level information disclosure risk.
From the tool's definition Tool name 'get_sql_generation_prompt' suggests retrieving a prompt template or documentation string. The empty description is uninformative, but the sibling tools (get_database_schema, get_query_examples, get_column_examples, get_database_overview) are all…
Documented attack patterns abuse exactly the kind of access get_sql_generation_prompt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JVLink MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_sql_generation_prompt:
{
"version": "1",
"default": "deny",
"tools": {
"get_sql_generation_prompt": {}
}
}get_sql_generation_prompt 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.
get_sql_generation_prompt. It is categorised as a Read tool in the JVLink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JVLink MCP Server MCP server in PolicyLayer and add a rule for get_sql_generation_prompt: 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 JVLink MCP Server. Nothing to install.
get_sql_generation_prompt 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 get_sql_generation_prompt 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 get_sql_generation_prompt. 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.
get_sql_generation_prompt is provided by the JVLink MCP Server MCP server (miyamamoto/jvlink-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JVLink 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.
25 JVLink MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.