This record as markdown: /tools/aws/import-parquet-to-table.md
What import_parquet_to_table does on AWS
AI agents use import_parquet_to_table to create or update resources in AWS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS environment.
Why import_parquet_to_table is rated Medium
The tool name strongly suggests importing external data (Parquet format) into a database table. This is a reversible write operation that modifies data state but does not delete or destroy existing records. The empty description limits confidence, but the naming convention combined with sibling tools on an AWS server (which includes data management and policy operations) supports classification as Write.
From the tool's definition Tool name 'import_parquet_to_table' indicates data ingestion/loading into a table, which is a write operation. Description is empty, reducing confidence.
Attacks that exploit this kind of access
The rule that runs import_parquet_to_table safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_parquet_to_table, this is the rule to start with:
import_parquet_to_table 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 AWS, apply this rule, and every import_parquet_to_table call is checked against it from then on.
Questions about import_parquet_to_table
import_parquet_to_table is a write tool on the AWS MCP server. It is categorised as a Write tool in the AWS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS MCP server in PolicyLayer and add a rule for import_parquet_to_table: 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 AWS. Nothing to install.
import_parquet_to_table 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_parquet_to_table 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_parquet_to_table. 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_parquet_to_table is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue