azure_sql_get_table_data
AI agents call azure_sql_get_table_data to retrieve information from Azure SQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix and positioning among sibling tools that include destructive operations (drop_table, delete_record) and write operations (create_record, update_record) indicates this tool retrieves data without modification. No side effects means low severity. Confidence reduced slightly due to empty description, but tool naming is sufficiently clear.
From the tool's definition Tool name is 'azure_sql_get_table_data' with 'get' prefix, indicating a retrieval operation. No description provided, but naming convention and context among sibling CRUD tools (create, update, delete, drop, execute_query) strongly suggests data retrieval…
Attacks that exploit this kind of access
azure_sql_get_table_data. It is categorised as a Read tool in the Azure SQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure SQL MCP Server MCP server in PolicyLayer and add a rule for azure_sql_get_table_data: 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 Azure SQL MCP Server. Nothing to install.
azure_sql_get_table_data 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 azure_sql_get_table_data 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 azure_sql_get_table_data. 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.
azure_sql_get_table_data is provided by the Azure SQL MCP Server MCP server (lostspace003/copilot-studio-azure-sql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →