Import minute bars from an external DuckDB database into the spot dataset via SpotStore.writeBars. The external database is ATTACHed read-only with alias
AI agents use import_from_database to create or update resources in Tradeblocks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tradeblocks environment.
An AI agent can call import_from_database faster than any human can review — one bad instruction and it creates or modifies resources in Tradeblocks by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Import minute bars from an external DuckDB database into the spot dataset via SpotStore.writeBars. The external database is ATTACHed read-only with alias. It is categorised as a Write tool in the Tradeblocks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tradeblocks MCP server in PolicyLayer and add a rule for import_from_database: 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 Tradeblocks. Nothing to install.
import_from_database 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 import_from_database 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 import_from_database. 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.
import_from_database is provided by the Tradeblocks MCP server (tradeblocks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.