오늘(또는 지정한 날짜)의 토큰 사용량을 Google Sheets에 제출합니다. 중복 제출은 자동 차단됩니다.
AI agents use submit_daily_report to create or update resources in MCP Token Tracker — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Token Tracker environment.
This tool creates new records in Google Sheets, a reversible data modification operation. It is Write rather than Execute because it performs a specific data submission action with defined behavior, not arbitrary command execution.
From the tool's definition Tool description states it 'submits token usage to Google Sheets' (오늘(또는 지정한 날짜)의 토큰 사용량을 Google Sheets에 제출합니다). This creates or modifies data in an external service (Google Sheets) by inserting usage records.
Attacks that exploit this kind of access
오늘(또는 지정한 날짜)의 토큰 사용량을 Google Sheets에 제출합니다. 중복 제출은 자동 차단됩니다. It is categorised as a Write tool in the MCP Token Tracker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Token Tracker MCP server in PolicyLayer and add a rule for submit_daily_report: 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 MCP Token Tracker. Nothing to install.
submit_daily_report 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 submit_daily_report 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 submit_daily_report. 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.
submit_daily_report is provided by the MCP Token Tracker MCP server (kdkim2000/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 →