AI agents call app-status to retrieve information from SupaThings MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'app-status' indicates a status check or query operation, which typically retrieves application state without side effects. While the description is empty (lowering confidence), the naming convention and context of a Things 3 management tool suggest this queries application state rather than modifying it. Status checks are read-only operations with minimal blast radius if misused.
From the tool's definition Tool named 'app-status' with empty description; contextual inference from sibling tools (get-*, add-*, etc.) and server purpose suggest status/query operation rather than modification
Documented attack patterns abuse exactly the kind of access app-status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SupaThings MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for app-status:
{
"version": "1",
"default": "deny",
"tools": {
"app-status": {}
}
}app-status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
app-status. It is categorised as a Read tool in the SupaThings MCP MCP Server, which means it retrieves data without modifying state.
Register the SupaThings MCP server in PolicyLayer and add a rule for app-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 SupaThings MCP. Nothing to install.
app-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 app-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 app-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.
app-status is provided by the SupaThings MCP server (soycanopa/supathings-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SupaThings MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 SupaThings MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.