Log an activity or event. If no session_id is provided, a session is automatically created or reused for the project. Just pass project_name and content — no need to start a session first.
Risk signalsAccepts raw HTML/template content (content)
Part of the ContextLayer server.
Free to start. No card required.
AI agents invoke log_activity to trigger processes or run actions in ContextLayer. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
log_activity can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"log_activity": {
"limits": [
{
"counter": "log_activity_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full ContextLayer policy for all 62 tools.
These attack patterns abuse exactly the kind of access log_activity gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Log an activity or event. If no session_id is provided, a session is automatically created or reused for the project. Just pass project_name and content — no need to start a session first.. It is categorised as a Execute tool in the ContextLayer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ContextLayer MCP server in PolicyLayer and add a rule for log_activity: 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 ContextLayer. Nothing to install.
log_activity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the log_activity 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_activity. 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_activity is provided by the ContextLayer MCP server (https://api.dotnova.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 62 ContextLayer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.