import_data
Import data from file into memory.db table
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/import-data.md
What import_data does on Project Guardian MCP
AI agents use import_data to create or update resources in Project Guardian MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Guardian MCP environment.
Why import_data is rated Medium
The tool writes data into a database table. While the operation is reversible (rows can be deleted or updated later), it modifies the database state. The severity is medium because uncontrolled imports could overwrite legitimate data or inject malicious records, but the damage is not irreversible like a Destructive operation and does not move money or execute arbitrary code like Execute tools.
From the tool's definition Tool description states 'Import data from file into memory.db table' — this creates or modifies data in the SQLite database by ingesting external file content, a reversible write operation.
Attacks that exploit this kind of access
The rule that runs import_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_data, this is the rule to start with:
import_data 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 Project Guardian MCP, apply this rule, and every import_data call is checked against it from then on.
Questions about import_data
Import data from file into memory.db table. It is categorised as a Write tool in the Project Guardian MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project Guardian MCP server in PolicyLayer and add a rule for import_data: 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 Project Guardian MCP. Nothing to install.
import_data 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_data 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_data. 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_data is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
This server
Across the catalogue