Log reading progress and update reading stats. Requires authorization.
Part of the SansFiction server.
Free to start. No card required.
AI agents use log_reading_progress to create or modify resources in SansFiction. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call log_reading_progress repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SansFiction.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"log_reading_progress": {
"limits": [
{
"counter": "log_reading_progress_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full SansFiction policy for all 16 tools.
These attack patterns abuse exactly the kind of access log_reading_progress gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Log reading progress and update reading stats. Requires authorization.. It is categorised as a Write tool in the SansFiction MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SansFiction MCP server in PolicyLayer and add a rule for log_reading_progress: 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 SansFiction. Nothing to install.
log_reading_progress 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 log_reading_progress 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_reading_progress. 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_reading_progress is provided by the SansFiction MCP server (hello-uvza/sansfiction). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 SansFiction 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.