Gmail 서비스 상태를 확인합니다.
AI agents call get_gmail_status to retrieve information from OOSDK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves the current status of the Gmail service—a read-only query. It has no side effects, does not modify data, execute code, delete anything, or move money. The minimal blast radius if misused would be information disclosure of service availability, which is typically non-sensitive operational data. Confidence is high because the name and description are unambiguous about its read-only nature.
From the tool's definition Tool name and description indicate it 'checks Gmail service status' (get_gmail_status / Gmail 서비스 상태를 확인합니다). This is a query/retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Gmail 서비스 상태를 확인합니다. It is categorised as a Read tool in the OOSDK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OOSDK MCP Server MCP server in PolicyLayer and add a rule for get_gmail_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 OOSDK MCP Server. Nothing to install.
get_gmail_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 get_gmail_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 get_gmail_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.
get_gmail_status is provided by the OOSDK MCP Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent_oosdk-public). 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 →