Check service terms signing status and API testing completion
AI agents call check_terms_status to retrieve information from Shioaji MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only lookup of administrative and testing status related to service terms and API configuration. It has no side effects, does not execute commands, does not modify data, and does not involve financial operations. The verb 'check' combined with 'status' clearly indicates a retrieval operation.
From the tool's definition Tool name 'check_terms_status' and description 'Check service terms signing status and API testing completion' indicate a query operation that retrieves status information without modifying data or triggering financial transactions.
Attacks that exploit this kind of access
Check service terms signing status and API testing completion. It is categorised as a Read tool in the Shioaji MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shioaji MCP Server MCP server in PolicyLayer and add a rule for check_terms_status: 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 Shioaji MCP Server. Nothing to install.
check_terms_status 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 check_terms_status 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 check_terms_status. 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.
check_terms_status is provided by the Shioaji MCP Server MCP server (offbeat-studio/shioaji-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →