AI agents call log-completed as a supporting operation in SupaThings MCP workflows.
The tool name suggests it may log or record completed tasks in Things 3, which could be a Write or Read operation. However, given the context of Things 3 task management and sibling tools like 'get-logbook' and 'empty-trash', it likely marks tasks as completed or moves them to the logbook — a Write operation. Confidence is low due to empty description. Defaulting to Other with medium severity pending clarification.
From the tool's definition Tool name is 'log-completed'; description is empty or uninformative.
Documented attack patterns abuse exactly the kind of access log-completed 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 log-completed:
{
"version": "1",
"default": "deny",
"tools": {
"log-completed": {
"limits": [
{
"counter": "log-completed_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}log-completed gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
log-completed. It is categorised as a Other tool in the SupaThings MCP MCP Server, which means it performs auxiliary operations.
Register the SupaThings MCP server in PolicyLayer and add a rule for log-completed: 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.
log-completed is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the log-completed 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 log-completed. 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.
log-completed 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.