list_contents
List content/lessons within a chapter.
This record as markdown: /tools/ackbarguppi-ai-thinkific-mcp/list-contents.md
What list_contents does on Thinkific MCP Server
AI agents call list_contents 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.
Why list_contents is rated Low
This tool retrieves and displays existing course content structure without modifying, deleting, or executing any operations. It is a straightforward data query with no destructive, financial, or executable side effects.
From the tool's definition Tool name 'list_contents' combined with description 'List content/lessons within a chapter' indicates a retrieval/query operation with no side effects. The verb 'list' is characteristic of Read category tools.
Attacks that exploit this kind of access
The rule that runs list_contents 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 list_contents, this is the rule to start with:
list_contents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Thinkific MCP Server, apply this rule, and every list_contents call is checked against it from then on.
Questions about list_contents
List content/lessons within a chapter. It is categorised as a Read tool in the Thinkific MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Thinkific MCP Server MCP server in PolicyLayer and add a rule for list_contents: 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.
list_contents 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 list_contents 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 list_contents. 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.
list_contents 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.
More on Thinkific MCP Server, and thousands of servers like it.
This server
Across the catalogue