check_table_access

Diagnose the connected service account\

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/check-table-access.md

WHAT IT DOES

What check_table_access does on ServiceNow-MCP

AI agents call check_table_access to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_table_access is rated Low

This tool queries or diagnoses access control information for the current service account. It is a read-only diagnostic operation that retrieves data about permissions and account status without side effects, making it a Read category tool. Severity is low because unauthorized disclosure of account access metadata poses minimal immediate risk compared to modification or deletion operations.

From the tool's definition Tool name 'check_table_access' and description 'Diagnose the connected service account' indicate a diagnostic query operation that retrieves information about access permissions and service account status without modifying or executing actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_table_access safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_table_access, this is the rule to start with:

check_table_access Allowed

check_table_access is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_table_access": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every check_table_access call is checked against it from then on.

FAQ

Questions about check_table_access

What does the check_table_access tool do? +

Diagnose the connected service account\. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_table_access? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for check_table_access: 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.

What risk level is check_table_access? +

check_table_access is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_table_access? +

Yes. Add a rate_limit block to the check_table_access 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.

How do I block check_table_access completely? +

Set action: deny in the PolicyLayer policy for check_table_access. 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.

What MCP server provides check_table_access? +

check_table_access 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.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →