Record file access for affinity scoring — boosts that file in future searches. Call after reading or editing a file.
AI agents use th0th_synapse_access to create or update resources in Th0th — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Th0th environment.
The tool writes/updates access records and affinity scores in the system's index. It modifies persistent state (scoring data) but does so reversibly and has minimal blast radius — misuse would only skew search rankings, not destroy or expose sensitive data.
From the tool's definition 'Record file access for affinity scoring — boosts that file in future searches'
Documented attack patterns abuse exactly the kind of access th0th_synapse_access gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Th0th, and nothing reaches the server without passing your rules. This is the rule we recommend for th0th_synapse_access:
{
"version": "1",
"default": "deny",
"tools": {
"th0th_synapse_access": {
"limits": [
{
"counter": "th0th_synapse_access_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}th0th_synapse_access 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.
Record file access for affinity scoring — boosts that file in future searches. Call after reading or editing a file. It is categorised as a Write tool in the Th0th MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Th0th MCP server in PolicyLayer and add a rule for th0th_synapse_access: 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 Th0th. Nothing to install.
th0th_synapse_access 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 th0th_synapse_access 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 th0th_synapse_access. 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.
th0th_synapse_access is provided by the Th0th MCP server (s1lv4/th0th). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Th0th tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Th0th tools catalogued and risk-classified — across an index of 42,500+ MCP servers.