check_grist

Check Grist spreadsheet/database service health via GET /api/docs. Returns 200 or 401 when service is up. Default port 8484.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

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/aaronckj-mcp-nettools/check-grist.md

WHAT IT DOES

What check_grist does on Mcp Nettools

AI agents call check_grist to retrieve information from Mcp Nettools 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_grist is rated Low

This is a health check that retrieves service status information without creating, modifying, deleting, or executing any operations. The GET request is a read-only operation that queries the Grist service endpoint to determine if it is operational. The low severity reflects that misuse would only result in repeated status queries, not resource exhaustion or unauthorized access to actual data.

From the tool's definition Tool performs a GET request to check service health status, returning HTTP status codes (200 or 401) with no side effects or data modification

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_grist safely

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

check_grist Allowed

check_grist 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_grist": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_grist call is checked against it from then on.

FAQ

Questions about check_grist

What does the check_grist tool do? +

Check Grist spreadsheet/database service health via GET /api/docs. Returns 200 or 401 when service is up. Default port 8484. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_grist? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_grist: 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 Mcp Nettools. Nothing to install.

What risk level is check_grist? +

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

Can I rate-limit check_grist? +

Yes. Add a rate_limit block to the check_grist 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_grist completely? +

Set action: deny in the PolicyLayer policy for check_grist. 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_grist? +

check_grist is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

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