gql_user_by_email

Returns a User by email address (GraphQL).

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/gql-user-by-email.md

WHAT IT DOES

What gql_user_by_email does on Thinkific MCP Server

AI agents call gql_user_by_email 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 gql_user_by_email is rated Low

This tool performs a simple lookup/retrieval of user information by email. It retrieves existing data without creating, modifying, or deleting anything, fitting the Read category.

From the tool's definition Tool description states 'Returns a User by email address' — a retrieval operation with no modification, creation, or deletion. GraphQL query syntax inherently queries data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gql_user_by_email 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 gql_user_by_email, this is the rule to start with:

gql_user_by_email Allowed

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

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 gql_user_by_email call is checked against it from then on.

FAQ

Questions about gql_user_by_email

What does the gql_user_by_email tool do? +

Returns a User by email address (GraphQL). 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 gql_user_by_email? +

Register the Thinkific MCP Server MCP server in PolicyLayer and add a rule for gql_user_by_email: 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 gql_user_by_email? +

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

Can I rate-limit gql_user_by_email? +

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

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

gql_user_by_email 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

The MCP Attack Database →

Guides

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