Get server-wide statistics including total documents, connections, and usage metrics
AI agents call get-server-statistics to retrieve information from Tiptap Collaboration MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns server statistics (total documents, connections, usage metrics) with no side effects, data modification, code execution, or destructive capability. It is a pure read operation used for monitoring and observability, making it a low-severity Read category tool.
From the tool's definition Tool name 'get-server-statistics' and description 'Get server-wide statistics including total documents, connections, and usage metrics' indicate a retrieval operation that queries aggregated server metrics without modifying any data or triggering external…
Documented attack patterns abuse exactly the kind of access get-server-statistics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tiptap Collaboration MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-server-statistics:
{
"version": "1",
"default": "deny",
"tools": {
"get-server-statistics": {}
}
} get-server-statistics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get server-wide statistics including total documents, connections, and usage metrics. It is categorised as a Read tool in the Tiptap Collaboration MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tiptap Collaboration MCP Server MCP server in PolicyLayer and add a rule for get-server-statistics: 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 Tiptap Collaboration MCP Server. Nothing to install.
get-server-statistics 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 get-server-statistics 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 get-server-statistics. 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.
get-server-statistics is provided by the Tiptap Collaboration MCP Server MCP server (trainual/tiptap-collaboration-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tiptap Collaboration MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Tiptap Collaboration MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.