state_board
CRUD operations on the cross-tool shared state board. TTL contract for set: omitting ttlSeconds defaults to 24h expiry; ttlSeconds: 0 means explicit permanent (no expiry, bounded only by the LRU cap); any other value is honored verbatim. NOTE: before this change, omitting ttlSeconds meant permane...
This record as markdown: /tools/io-github-vmoranv-jshookmcp/state-board.md
What state_board does on Jshookmcp
AI agents use state_board to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.
Why state_board is rated Medium
Creates, modifies, or deletes shared state data reversibly with TTL management; not destructive due to reversibility and TTL constraints.
From the tool's definition CRUD operations on shared state board; set, get, delete functionality
Attacks that exploit this kind of access
The rule that runs state_board safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For state_board, this is the rule to start with:
state_board 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every state_board call is checked against it from then on.
Questions about state_board
CRUD operations on the cross-tool shared state board. TTL contract for set: omitting ttlSeconds defaults to 24h expiry; ttlSeconds: 0 means explicit permanent (no expiry, bounded only by the LRU cap); any other value is honored verbatim. NOTE: before this change, omitting ttlSeconds meant permanent — this is a behavior change. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jshook MCP server in PolicyLayer and add a rule for state_board: 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 Jshookmcp. Nothing to install.
state_board 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 state_board 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 state_board. 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.
state_board is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue