AI agents invoke execute_template_query to trigger actions in JVLink 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.
This tool generates SQL from templates and executes them against a database. While the template-based approach constrains flexibility compared to arbitrary SQL execution, it still runs code (SQL) whose side effects depend on template parameters and database state.
From the tool's definition Tool name 'execute_template_query' combined with description 'テンプレートからSQLを生成して実行' (Generate SQL from template and execute) indicates the tool generates and executes SQL queries. The 'execute' verb and SQL execution capability place it in the Execute category.
Documented attack patterns abuse exactly the kind of access execute_template_query 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 execute_template_query:
{
"version": "1",
"default": "deny",
"tools": {
"execute_template_query": {
"limits": [
{
"counter": "execute_template_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_template_query 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.
テンプレートからSQLを生成して実行. It is categorised as a Execute tool in the JVLink MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the JVLink MCP Server MCP server in PolicyLayer and add a rule for execute_template_query: 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.
execute_template_query 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 execute_template_query 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 execute_template_query. 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.
execute_template_query 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.