get_projects
Selected work. Optionally filter by tag (AI, Fintech, Blockchain, NFT).
This record as markdown: /tools/com-frankponcelet-profile/get-projects.md
What get_projects does on Profile
AI agents call get_projects to retrieve information from Profile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | — | Case-insensitive tag filter. Known tags: AI, Fintech, Blockchain, NFT. |
Parameters from the server's own tool schema.
Why get_projects is rated Low
This tool retrieves project information with optional filtering. It performs a simple query operation with no side effects, no code execution, and no data modification. The read-only server designation and the passive 'get' verb confirm this is a safe data retrieval tool.
From the tool's definition Tool name is 'get_projects' with description 'Selected work' and filter-only capability. Server is explicitly described as 'Read-only MCP server'. No mutation, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs get_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Profile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_projects, this is the rule to start with:
get_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Profile, apply this rule, and every get_projects call is checked against it from then on.
Questions about get_projects
Selected work. Optionally filter by tag (AI, Fintech, Blockchain, NFT). It is categorised as a Read tool in the Profile MCP Server, which means it retrieves data without modifying state.
get_projects accepts 1 parameter: tag. The full parameter table on this page comes from the server's own tool schema.
Register the Profile MCP server in PolicyLayer and add a rule for get_projects: 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 Profile. Nothing to install.
get_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_projects 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 get_projects. 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.
get_projects is provided by the Profile MCP server (https://frankponcelet.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Profile, and thousands of servers like it.
This server
Across the catalogue