gql_update_assignment_submission
Update the status of an assignment submission (GraphQL). Valid statuses: APPROVED, PENDING, REJECTED.
This record as markdown: /tools/ackbarguppi-ai-thinkific-mcp/gql-update-assignment-submission.md
What gql_update_assignment_submission does on Thinkific MCP Server
AI agents use gql_update_assignment_submission to create or update resources in Thinkific MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thinkific MCP Server environment.
Why gql_update_assignment_submission is rated Medium
This tool modifies assignment submission records by changing their status, which is a write operation. While the change is reversible (status can be updated again), the action affects student records and learning progress tracking, giving it medium severity due to potential impact on student academic records and course administration.
From the tool's definition Tool name contains 'update' and description states 'Update the status of an assignment submission', indicating modification of existing data. The status change (APPROVED, PENDING, REJECTED) is reversible since the tool allows updating to different states.
Attacks that exploit this kind of access
The rule that runs gql_update_assignment_submission 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_update_assignment_submission, this is the rule to start with:
gql_update_assignment_submission stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 gql_update_assignment_submission call is checked against it from then on.
Questions about gql_update_assignment_submission
Update the status of an assignment submission (GraphQL). Valid statuses: APPROVED, PENDING, REJECTED. It is categorised as a Write tool in the Thinkific MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Thinkific MCP Server MCP server in PolicyLayer and add a rule for gql_update_assignment_submission: 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.
gql_update_assignment_submission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gql_update_assignment_submission 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 gql_update_assignment_submission. 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.
gql_update_assignment_submission 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