AI agents use save_session_log to create or update resources in MCPacer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCPacer environment.
The 'save_' prefix strongly implies writing/creating data rather than reading, deleting, or executing external commands. Within the Strava coaching context, a session log would likely be a new record in the dashboard or database. However, the empty description introduces uncertainty about whether it might have unexpected side effects or scope.
From the tool's definition Tool name 'save_session_log' suggests creating or storing a log record. The empty description prevents definitive classification, but the 'save_' prefix indicates a write operation.
Documented attack patterns abuse exactly the kind of access save_session_log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPacer, and nothing reaches the server without passing your rules. This is the rule we recommend for save_session_log:
{
"version": "1",
"default": "deny",
"tools": {
"save_session_log": {
"limits": [
{
"counter": "save_session_log_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_session_log stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
save_session_log. It is categorised as a Write tool in the MCPacer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCPacer MCP server in PolicyLayer and add a rule for save_session_log: 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 MCPacer. Nothing to install.
save_session_log 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 save_session_log 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 save_session_log. 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.
save_session_log is provided by the MCPacer MCP server (wernerpe/mcpacer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCPacer, 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.
32 MCPacer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.