azure_sql_get_table_schema
AI agents call azure_sql_get_table_schema 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.
Schema inspection is a non-destructive metadata retrieval operation. The naming convention and context of sibling tools confirm this is a Read operation. No modification, execution, deletion, or financial impact is possible. Severity is low as schema information alone poses minimal risk; an AI agent misusing this tool would at worst retrieve unwanted schema details, but cannot alter data or execute code.
From the tool's definition Tool name 'azure_sql_get_table_schema' indicates retrieval of table schema metadata; sibling tools show this server's vocabulary uses 'get_' prefix for read operations (e.g., 'azure_sql_get_database_info', 'azure_sql_get_table_data').
Attacks that exploit this kind of access
azure_sql_get_table_schema. 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_schema: 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_schema 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_schema 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_schema. 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_schema 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 →