my_packs

List the user’s pack proposals with status (submitted, approved + pack URL, rejected + reason) and the status of each member model.

SERVER3dassets SOURCE3dassets-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3dassets-mcp/my-packs.md

WHAT IT DOES

What my_packs does on 3dassets

AI agents call my_packs to retrieve information from 3dassets without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why my_packs is rated Low

Even though my_packs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs my_packs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 3dassets, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For my_packs, this is the rule to start with:

my_packs Allowed

my_packs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "my_packs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 3dassets, apply this rule, and every my_packs call is checked against it from then on.

FAQ

Questions about my_packs

What does the my_packs tool do? +

List the user’s pack proposals with status (submitted, approved + pack URL, rejected + reason) and the status of each member model. It is categorised as a Read tool in the 3dassets MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on my_packs? +

Register the 3dassets MCP server in PolicyLayer and add a rule for my_packs: 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 3dassets. Nothing to install.

What risk level is my_packs? +

my_packs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit my_packs? +

Yes. Add a rate_limit block to the my_packs 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.

How do I block my_packs completely? +

Set action: deny in the PolicyLayer policy for my_packs. 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.

What MCP server provides my_packs? +

my_packs is provided by the 3dassets MCP server (3dassets-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 3dassets, and thousands of servers like it.

This server

All 20 3dassets tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →