AI agents call get_syntax_help to retrieve information from Tdsql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The empty description lowers confidence, but the name and context (Teradata analytics agent with reference tools like describe_table, list_databases, list_tables) indicate this likely retrieves syntax documentation or help text. No indication of data modification, execution, deletion, or financial operations. Classified as Read with medium-low confidence due to lack of explicit description.
From the tool's definition Tool name 'get_syntax_help' suggests retrieval of documentation or syntax information, consistent with a Read category tool that queries reference material without side effects.
Documented attack patterns abuse exactly the kind of access get_syntax_help gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tdsql, and nothing reaches the server without passing your rules. This is the rule we recommend for get_syntax_help:
{
"version": "1",
"default": "deny",
"tools": {
"get_syntax_help": {}
}
}get_syntax_help 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_syntax_help. It is categorised as a Read tool in the Tdsql MCP Server, which means it retrieves data without modifying state.
Register the Tdsql MCP server in PolicyLayer and add a rule for get_syntax_help: 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 Tdsql. Nothing to install.
get_syntax_help 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_syntax_help 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_syntax_help. 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_syntax_help is provided by the Tdsql MCP server (ksturgeon-td/tdsql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tdsql, 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.
7 Tdsql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.