get_site_info

Get overview information about the connected Thinkific site by fetching course and user counts.

SERVERThinkific MCP Server SOURCEackbarguppi-ai/thinkific-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/ackbarguppi-ai-thinkific-mcp/get-site-info.md

WHAT IT DOES

What get_site_info does on Thinkific MCP Server

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

RISK

Why get_site_info is rated Low

This tool retrieves aggregate site statistics (course counts, user counts) without modifying any data or triggering actions. It is a straightforward read operation with minimal risk; disclosure of such summary metrics poses low security concern.

From the tool's definition Tool name 'get_site_info' and description 'Get overview information about the connected Thinkific site by fetching course and user counts' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_site_info safely

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

get_site_info Allowed

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

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

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

FAQ

Questions about get_site_info

What does the get_site_info tool do? +

Get overview information about the connected Thinkific site by fetching course and user counts. It is categorised as a Read tool in the Thinkific MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_site_info? +

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

What risk level is get_site_info? +

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

Can I rate-limit get_site_info? +

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

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

get_site_info is provided by the Thinkific MCP Server MCP server (ackbarguppi-ai/thinkific-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Thinkific MCP Server, and thousands of servers like it.

This server

All 109 Thinkific MCP Server tools →

Across the catalogue

get_team_info on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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