Analyze data quality and field completeness for a ServiceNow table —
AI agents call check_table_completeness to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes metadata about a ServiceNow table to assess data quality and completeness. It performs queries and analysis only, with no side effects on data—no creation, modification, deletion, or triggering of external operations. It falls squarely into the Read category (retrieves or queries data).
From the tool's definition Tool name 'check_table_completeness' and description 'Analyze data quality and field completeness for a ServiceNow table' indicates a data analysis and inspection function with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Analyze data quality and field completeness for a ServiceNow table —. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for check_table_completeness: 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 ServiceNow-MCP. Nothing to install.
check_table_completeness 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 check_table_completeness 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 check_table_completeness. 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.
check_table_completeness is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-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 →