This record as markdown: /tools/io-github-devopam-mcpg/import-json.md
What import_json does on Mcpg
AI agents use import_json to create or update resources in Mcpg, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcpg environment.
Why import_json is rated Medium
Without explicit description, the name 'import_json' strongly suggests inserting or loading JSON data into PostgreSQL, which is a Write operation (reversible modification). Severity is high because unvalidated JSON imports could corrupt data schemas or introduce malicious payloads into production.
From the tool's definition Tool named 'import_json' on a PostgreSQL MCP server; 'import' typically indicates data ingestion that modifies the database state. Sibling tools show this server manages data policies, query analysis, and database operations.
Attacks that exploit this kind of access
The rule that runs import_json safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_json, this is the rule to start with:
import_json 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 Mcpg, apply this rule, and every import_json call is checked against it from then on.
Questions about import_json
import_json is a write tool on the Mcpg MCP server. It is categorised as a Write tool in the Mcpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcpg MCP server in PolicyLayer and add a rule for import_json: 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 Mcpg. Nothing to install.
import_json 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_json 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_json. 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_json is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue