get_unread_count
读取当前配置账号的未读计数,不打开通知列表、不标记已读。来源是站点身份接口 user.me 随身份返回的三个计数:prompt(提醒)、pm(私信)、chat(聊天),按站点实际提供的类别输出。站点没给或不是整数的计数为 null 并列入 missing,未知不当作零;登录失效返回 status=failed 且各计数为 null,不当作没有通知。read_at 为读取时刻(UTC)。
This record as markdown: /tools/1point3acres-toolkit/get-unread-count.md
What get_unread_count does on 1point3acres Toolkit
AI agents call get_unread_count to retrieve information from 1point3acres Toolkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_unread_count is rated Low
Retrieves notification counts without side effects or data modification.
From the tool's definition reads unread count, does not open notifications, does not mark as read
Attacks that exploit this kind of access
The rule that runs get_unread_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1point3acres Toolkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_unread_count, this is the rule to start with:
get_unread_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1point3acres Toolkit, apply this rule, and every get_unread_count call is checked against it from then on.
Questions about get_unread_count
读取当前配置账号的未读计数,不打开通知列表、不标记已读。来源是站点身份接口 user.me 随身份返回的三个计数:prompt(提醒)、pm(私信)、chat(聊天),按站点实际提供的类别输出。站点没给或不是整数的计数为 null 并列入 missing,未知不当作零;登录失效返回 status=failed 且各计数为 null,不当作没有通知。read_at 为读取时刻(UTC)。. It is categorised as a Read tool in the 1point3acres Toolkit MCP Server, which means it retrieves data without modifying state.
Register the 1point3acres Toolkit MCP server in PolicyLayer and add a rule for get_unread_count: 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 1point3acres Toolkit. Nothing to install.
get_unread_count 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_unread_count 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_unread_count. 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_unread_count is provided by the 1point3acres Toolkit MCP server (vivian-labs/1point3acres-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1point3acres Toolkit, and thousands of servers like it.
This server
Across the catalogue